Skip to content
This repository has been archived by the owner. It is now read-only.

npm install --time-machine (ignore packages released after a given date) #12994

Closed
jedwards1211 opened this issue Jun 7, 2016 · 6 comments

Comments

@jedwards1211
Copy link

commented Jun 7, 2016

Recently I've run into an issue where a new version of some transitive dependency of babel-eslint fails to parse Flow parameterized types. Downgrading babel-eslint didn't work because the newer versions of the transitive deps are semver-compatible with the older version of babel-eslint.

Since a fresh npm install worked fine several months ago, if there was a time machine-like feature whereby it would install exactly the same packages as it would have on a specific date several months ago, I should be able to get a working project setup again, because I would get all the older versions of all the transitive dependencies.

I can't think of any simpler way to get a working project setup, because I've lost a working copy with all the old transitive deps that worked.

@jedwards1211 jedwards1211 changed the title Feature request: npm install time machine (ignore packages released after a given date) Feature request: npm install --time-machine (ignore packages released after a given date) Jun 8, 2016

@othiym23 othiym23 changed the title Feature request: npm install --time-machine (ignore packages released after a given date) npm install --time-machine (ignore packages released after a given date) Jun 14, 2016

@DaveEmmerson

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2017

@jedwards1211 This would be great... but given it's almost a year later, how did you solve your issue? I'm facing a similar problem and my first thought is to run the dependency list through npm to get versions and release dates (if that's possible) and run them through a script to filter out the newer ones.

@jedwards1211

This comment has been minimized.

Copy link
Author

commented Apr 4, 2017

I did solve it using this fork... You could use it temporarily to install what you need, then shrinkwrap and switch back to official npm. Let me know if you need help installing/running this fork.

@DaveEmmerson

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2017

I don't see the fork in your list of repositories. I can see the other issue referenced and the changes on there, but the fork doesn't show. Any clue? I could try to pull npm from the date of your commits and just apply the changes, but if the fork is still around somewhere that would be easier :)

@jedwards1211

This comment has been minimized.

Copy link
Author

commented Apr 4, 2017

@DaveEmmerson

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2017

@npm-robot

This comment has been minimized.

Copy link

commented Jun 19, 2017

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Jun 19, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants
You can’t perform that action at this time.