Skip to content
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

[FEATURE PROPOSAL] npm-versions.json #28

Open
ilan-schemoul opened this issue Mar 13, 2017 · 2 comments
Open

[FEATURE PROPOSAL] npm-versions.json #28

ilan-schemoul opened this issue Mar 13, 2017 · 2 comments

Comments

@ilan-schemoul
Copy link

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.

@SidneyNemzer
Copy link

SidneyNemzer commented Aug 18, 2017

I think it's a great idea! Saving your dependencies is a key part of package management.

Another possible way to save the versions would be to add a key to the package.json file, like so:

{
  "name": "...",
  "version": "1.0.0",
  "dependencies": {
    "react": "^0.23.0"
  },
  "npm-install-version": {
    "material-ui": [
       "0.2.0",
       "@next"
     ]
  }
}

@scott113341
Copy link
Owner

@NitroBAY and @SidneyNemzer this is a great idea. I'd happily accept a PR adding this functionality!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants