You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the things I have noticed is dependencies are not added to clib.json when clib install is called. This would make this easier to use than it already is.
The text was updated successfully, but these errors were encountered:
I looked at the clib code because I wanted to implement this and found that the feature is already there. Run install with the -S or --save flag.
Seems this behavior was inspired by npm, which as of v5 saves deps to package.json by default (ref). Nowadays npm supports --no-save (or -no- prepended to pretty much any flag) to negate the behavior.
This makes more sense to me as a default behavior. If the maintainers are good with it, I'll make the change.
I looked at the clib code because I wanted to implement this and found that the feature is already there. Run install with the -S or --save flag.
Seems this behavior was inspired by npm, which as of v5 saves deps to package.json by default (ref). Nowadays npm supports --no-save (or -no- prepended to pretty much any flag) to negate the behavior.
This makes more sense to me as a default behavior. If the maintainers are good with it, I'll make the change.
One of the things I have noticed is dependencies are not added to clib.json when clib install is called. This would make this easier to use than it already is.
The text was updated successfully, but these errors were encountered: