-
Notifications
You must be signed in to change notification settings - Fork 43
Improve handling of repo on new app #12
Comments
I was confused at this line, because it didn't give any example.
It made me wonder - should I enter So help text would be nice. Like example value on the right or greyed out. |
On further inspection, I see the value actually gets used here in the template: lib/generators/blog/templates/package.json
Based on working with {
"repository": "https://github.com/my-user/my-app"
} I left it blank. Which then gave me a result like this with a forward slash {
"repository": "/my-app"
} So leaving out repo seems to get weird behavior. And if I entered {
"repository": "https://github.com/my-user/my-app/my-app",
} So that looks like a bug. What I would expect is that the app should ask for "Repo URL" so there is no confusion. e.g. And then that whole value should appear in the result. Which means a code change. Maybe even name the variable repoUrl instead of repo. - "repository": "<%= repo %>/<%= name %>"
+ "repository": "<%= repo %>" Or ask the user for path to their GitHub account (not their repo)- e.g.
Then this makes sense with a rename. - "repository": "<%= repo %>/<%= name %>"
+ "repository": "<%= userUrl %>/<%= name %>" Or leave out repo as a question and output field altogether. |
Any way to solve this issue? C:\Users\JRIVERA\AppData\Roaming\npm-cache_npx\11860\node_modules\create-vuepress-site\node_modules\mem-fs-editor\node_modules\mkdirp\lib\path-arg.js:20 Error: Illegal characters in path. this jumps even when I leave the question blank, or typing something. |
This issue was created as general improvement of code and documentation. You have a very specific error, possibly specific to your OS or the fields you are entering. Perhaps you can make an new issue instead and link it here. Also it might get more attention that way, as this issue from 2021 hasn't had activity otherwise. |
I don't know why, but, this error only jumps in my home computer, at work all go with shining colors. Maybe is something in my setup. Sorry for post it here, I think the project was alive, and the issue also. |
Hi
I ran the command to setup an app.
I was confused by the
repo
argument, in how it appears in the interactive CLI and how it gets used.Suggestions:
npm i
.The text was updated successfully, but these errors were encountered: