-
Notifications
You must be signed in to change notification settings - Fork 355
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
renaming the project #85
Comments
You can use your shell feature named alias I wrote small example for you: alias yorw="yo react-webpack" You can make this permanent with adding that line to your ~/.bashrc. |
That's the exact route I was thinking after realising this was out of scope for yeoman 👍 thanks Max On Saturday, 11 Apr 2015 at 16:45, Max Sysoev notifications@github.com, wrote: You can use your shell feature named alias I wrote small example for you: export yorw="yo react-webpack" You can make this permanent with adding that line to your ~/.bashrc. — |
I disagree with this solution. |
Sorry, I disagree with that. Using aliases for abbreviations is not a hack, its one of their main use cases. I don't know if you use Windows (because of your "unix thing" comment) but I bet that the Windows command line tools have some way of defining aliases, too. Abbreviations and such are a very subjective thing, similar to keyboard shortcuts and as such should be handled in your terminal configuration and not by renaming the project. (There is also a zsh plugin that gives you auto-completion of generator names.) |
Iv'e tried with windows, so instead of |
@yonatanmn sorry I've forgot about subgenerators. Hm.. this is a hard issue... Ha! What about npm scopes? With 'em it's possible to place this generator like |
The problem is with how Yeoman will read this, stating it is only looking for |
Honestly, I still don't see the point. If subgenerators don't work, use |
In windows, tried : |
I don't have a Windows machine, but did you try |
the correct way is what i quoted before (that's why it gave 'no name' error). Tried yours just to make sure - not working at all. |
Yes
Then you can do:
|
Ok, but still no windows solution... |
What about cygwin or PowerShell? |
I'll check them out. |
For every operation, one needs to write
yo react-webpack
, quite long I assume.There is no workaround for alias name, so the only option is to rename the entire project.
generator-react
is already taken. Can anyone think about a cool and short name?The text was updated successfully, but these errors were encountered: