Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EDGE CASE] Bad preset naming might break the functionality. #1871

Closed
serkanyersen opened this issue Jul 16, 2018 · 2 comments · Fixed by #1874
Closed

[EDGE CASE] Bad preset naming might break the functionality. #1871

serkanyersen opened this issue Jul 16, 2018 · 2 comments · Fixed by #1874

Comments

@serkanyersen
Copy link
Contributor

Version

3.0.0-rc.5

Reproduction link

https://github.com/vuejs/vue-cli

Steps to reproduce

I know this is the wrong usage, but when I initially used the presets I though it was going to create a preset file in the directory. so when asked I named the preset as project.json

  • vue create project

  • select any option you want, on the last step, say Y to Save this as a preset for future projects?

  • Type project.json to Save preset as: question. It could be anything, just add an extension to the name.

  • type vue create again, and select project.json should appear at the top.

What is expected?

I guess it should initiate the preset without error. or it shouldn't let me type invalid name for a preset in the first place.

What is actually happening?

vue create fails with Error: ENOENT: no such file or directory, open 'project.json' error
screen shot 2018-07-16 at 14 20 59


Also couldn't find a way to list or edit the presets after they are created. only way seems to be manually editing ~/.vuerc file. Which is totally fine, just wanted to point out.

@LinusBorg
Copy link
Member

LinusBorg commented Jul 16, 2018

Also couldn't find a way to list or edit the presets after they are created.

There's already a PR for a new vue config command that will address this.

Edit: now I can't find it anymore...

@serkanyersen
Copy link
Contributor Author

I think it's #1554. Looks like it's merged already. Awesome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants