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

es-abstract 1.14.0 no longer exists in npm #55

Closed
akotranza opened this issue Sep 4, 2019 · 6 comments
Closed

es-abstract 1.14.0 no longer exists in npm #55

akotranza opened this issue Sep 4, 2019 · 6 comments

Comments

@akotranza
Copy link

Hi, 1.14.0 no longer exists on npm as of a couple hours ago which is blowing up whatever version of webpack I'm using. Will hack around it in package-lock.json, but kind of a problem when versions disappear 😄

@ljharb
Copy link
Owner

ljharb commented Sep 4, 2019

Indeed, i apologize for the inconvenience - it hadn’t been 24 hours yet, and it had files in it that it shouldn’t have. v1.14.1 is already published, before i unpublished v1.14.0, so it should be trivial to update it in your lockfile.

@ljharb ljharb closed this as completed Sep 4, 2019
@ljharb

This comment has been minimized.

@bj00rn
Copy link

bj00rn commented Nov 1, 2019

@ljharb first off thanks for your efforts! 🙏

Maybe add a temporary note to readme about this version being removed, since ppl are still ending up here.

I Didn't get this error until i wiped my yarn cache..

@ljharb
Copy link
Owner

ljharb commented Nov 1, 2019

It’d be helpful if someone could help shed light on what package out there is still depending on 1.14.0. This package is on v1.16.0 now.

@bj00rn
Copy link

bj00rn commented Nov 1, 2019

It’d be helpful if someone could help shed light on what package out there is still depending on 1.14.0. This package is on v1.16.0 now.

The problem for me was that I couldn't even do a yarn install once i nuked my cache, since I had 1.14.0 resolved in my lock file. I had to edit the file manually and remove the 'resolved' url. I after that I did a yarn install and yarn set me up with 1.16.1.

@ljharb
Copy link
Owner

ljharb commented Nov 1, 2019

Sounds like a bug to file on yarn, as an unpublished package in the lockfile is something that clearly can happen.

rmacklin added a commit to rails-front-end/external_asset_pipeline that referenced this issue Dec 13, 2019
Version 1.14.0 has been removed from the npm registry [1], so
`yarn install` was failing with:
```
error An unexpected error occurred: "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.14.0.tgz: Request failed \"404 Not Found\"".
```
Upgrading to 1.14.1 fixes this.

[1]: ljharb/es-abstract#55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants