-
Notifications
You must be signed in to change notification settings - Fork 255
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
notion install behavior surprising compared to yarn/npm #364
Comments
This is interesting, and given that we are working in the Node space, I wonder if we shouldn't also update the command to support |
That would make sense to me. It would require an RFC I expect. |
I can write that RFC if people like—the more I use it the more I think that should be the behavior, but I'd like input from @dherman, @mikrostew, @rwjblue, and any other interested parties before I commit to writing that. |
I think an RFC for this would be great - I like this behavior |
Consensus when I asked everybody who could make it to a meeting about release cadences was this was good; I'll write the RFC for it tomorrow. Closing this in favor of that. |
…reopening because I realize that assuming we accept such an RFC, I should close this when its implementation merges. |
Closed by #383. |
Currently
notion install
only allows a single package to be installed at a time. Users' expectation will probably be that multiple packages can be installed simultaneously, as this is the behavior ofnpm install
andyarn add
(both locally and with--global
option). Given that we default to installing latest if a version is not specified, could we support this in the install command so that a user could, for example, donotion install typescript ember-cli ts-node
?The text was updated successfully, but these errors were encountered: