Allow vue-create Presets to Target Github Enterprise
See original GitHub issueWhat problem does this feature solve?
My company uses github enterprise so the preset we want to target is not located on github.com, gitlab.com, or bitbucket.com.
I would like to be able to run the command vue create --preset <url to my company's private github instance>
or some other mechanism to indicate the domain.
What does the proposed API look like?
vue create -preset <domain>/repo_name
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Plugins and Presets - Vue CLI
When you use vue create to create a new project, some plugins will be pre-installed for you based on your feature selection.
Read more >Creating a new Vue project - Educative.io
To do that, run the command vue create [project name]. For example, let's create a project named hello-world: vue create hello-world.
Read more >Vue JavaScript Tutorial in Visual Studio Code
Vue JavaScript tutorial showing IntelliSense, debugging, and code navigation support in the Visual Studio Code editor.
Read more >Can I create vue-cli project without Git? - Stack Overflow
From the docs: Usage: create [options] <app-name>. create a new project powered by vue-cli-service. Options: -p, --preset <presetName> Skip ...
Read more >How to Use Vue CLI for Easier VueJS Project Management
Choose npm . Overwrite the target folder if it exists already. Initialize a git repository and specify the initial commit message. Enable this ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can this ticket be re-opened since it wasn’t actually fixed and was closed before any confirmation was made over whether it was fixed?
We are aware of and are using the workaround of having the generator repo pulled down locally, but this means that the user will need to manage their local repo in order to use the generator. By adding a way to set up the domain to use Github Enterprise, we can ensure developers are consistently using the same, most up-to-date version of the generator.