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
Hello,
Wouldn't this would be a good idea to have a npm-versions.json (or whatever) to follow npm scheme because I may use this in production.
In my use case I need to have both the @next and the current version of a UI framework. In any way in package.json I may put "postinstall": "niv material-ui@next" but being able to do a niv material-ui@next --save so in a npm-versions.json there will be as a dependency material-ui@next and then in package.json one'd put "postinstall": "niv i.
But it's maybe a dumb idea.
The text was updated successfully, but these errors were encountered:
Hello,
Wouldn't this would be a good idea to have a npm-versions.json (or whatever) to follow npm scheme because I may use this in production.
In my use case I need to have both the
@next
and the current version of a UI framework. In any way inpackage.json
I may put"postinstall": "niv material-ui@next"
but being able to do aniv material-ui@next --save
so in anpm-versions.json
there will be as a dependencymaterial-ui@next
and then inpackage.json
one'd put"postinstall": "niv i
.But it's maybe a dumb idea.
The text was updated successfully, but these errors were encountered: