-
Notifications
You must be signed in to change notification settings - Fork 642
published package tarball includes node_modules/history #133
Comments
Should be fixed by #134. @jlongster Should we do a new release? We could do a 1.0.2 directly off the 1.0.1 tag so we don't include the breaking(?) change related to init path on master. |
Hm, usually I like versions to be direct ancestors, but it is kind of annoying that we're still changing APIs and not able to push minor fixes. I guess there's nothing really wrong with cherry-picking changes for a minor release. |
Ok I just cherry-picked that change and published 1.0.2. Does that fix this issue? |
Thank you! What npm version did you use it? Does it match There are two ways for avoiding this issue
You can test for this using This is the npm scoped package which is fixed the issue. |
Any progress? |
Sorry, not yet. My npm version is 2.14.7. What changed in the later versions to fix this? I can upgrade before releasing 2.0.0. |
@jlongster npm/fstream-npm#15 |
My comment has mistake 😖
correct: You should use npm version |
@jlongster Can you bump your version of NPM ( |
Whoops, I meant to do that before I published. About to head to bed but I'll do it first thing in the morning. |
Should be fixed. Just published 2.0.3 with npm 3.5.3. |
Nope :( https://registry.npmjs.org/redux-simple-router/-/redux-simple-router-2.0.3.tgz We had this issue on react-router, but I forget how it was resolved. Paging @taion! |
weird! |
It's resolved if you use npm2 :p The bug wasn't properly fixed for npm3. Otherwise, you can use something like https://github.com/rackt/react-router/blob/6bddfccd4d52dd0ab33298e91b13ed21f68e1135/scripts/release.sh#L52-L57. |
|
@jlongster This was not fixed in 2.0.3. Until npm/npm#10445 is merged, this will be broken in every version of npm3. You need to either use a recent npm2 or use the workaround of deleting |
Sorry, I gave you incorrect information. |
Yeesh, sorry it took so long to get around to this :/ This was a holiday weekend. I'm adding @timdorr, who's done an awesome job cleaning up issues, as a publisher on npm so I'm not the bottleneck there. |
thanks @jlongster |
Just pushed 2.0.4 with the fixed package. |
COOL, thanks! @timdorr |
Thanks! 🎉 |
Currently,
redux-simple-router-1.0.1.tgz
includesnode_modules/history
.Because of this,
npm shrinkwrap
fails.Related issues to this are here.
Can you republish this with
npm@>2.14.10 || >3.4.0
?The text was updated successfully, but these errors were encountered: