Skip to content

No files published to npm in v0.5.0 #131

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

Closed
danburzo opened this issue Mar 7, 2021 · 5 comments
Closed

No files published to npm in v0.5.0 #131

danburzo opened this issue Mar 7, 2021 · 5 comments

Comments

@danburzo
Copy link

danburzo commented Mar 7, 2021

Hi there, we're trying to use this package with node-fetch v2.x to prepare for v3.x and we noticed there are no files on npm for the v0.5.0 version.

@Richienb
Copy link
Member

Richienb commented Aug 6, 2021

Fixed in 0.6.0

@Richienb Richienb closed this as completed Aug 6, 2021
@danburzo
Copy link
Author

danburzo commented Aug 6, 2021

Thanks @Richienb! However, I seem to be getting an error when attempting npm install fetch-charset-detection. I'm on node v16.5.0 / npm 7.19.1.

Error output
npm install fetch-charset-detection
npm WARN tarball tarball data for fetch-charset-detection@https://registry.npmjs.org/fetch-charset-detection/-/fetch-charset-detection-0.6.0.tgz (sha512-lq5uuET/3AVAxkxHZRcgi0Vq5uQHVvwv6cxvQqQHIlmjLtAQ6eGhk2O9i8nSnZcQgrB8t+8bDPJGjBXDQQIWxA==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for fetch-charset-detection@https://registry.npmjs.org/fetch-charset-detection/-/fetch-charset-detection-0.6.0.tgz (sha512-lq5uuET/3AVAxkxHZRcgi0Vq5uQHVvwv6cxvQqQHIlmjLtAQ6eGhk2O9i8nSnZcQgrB8t+8bDPJGjBXDQQIWxA==) seems to be corrupted. Trying again.
npm ERR! code EINTEGRITY
npm ERR! sha512-lq5uuET/3AVAxkxHZRcgi0Vq5uQHVvwv6cxvQqQHIlmjLtAQ6eGhk2O9i8nSnZcQgrB8t+8bDPJGjBXDQQIWxA== integrity checksum failed when using sha512: wanted sha512-lq5uuET/3AVAxkxHZRcgi0Vq5uQHVvwv6cxvQqQHIlmjLtAQ6eGhk2O9i8nSnZcQgrB8t+8bDPJGjBXDQQIWxA== but got sha512-IiRQjHX+GhiLi8rbBwa65DThvvYw7hAa6UQHTanNskw9EFFNJkh5uMyrzXwOzNGLUD62s/wzIBVK+khlT97aOg==. (3400 bytes)

@Richienb
Copy link
Member

Richienb commented Aug 6, 2021

I think that's an issue on npm's side

@danburzo
Copy link
Author

Hi again, @Richienb. I'm switching to ESM downstream, and I'm hit by this error again. I have cloned the repo and republished under @danburzo/fetch-charset-detection and npm install works as expected. However, I'm still getting an integrity error for the original package.

I'm not sure this can be fixed from the NPM side (example issue from March). Would you be willing to try republishing from under the latest npm 6.x / 7.x version?

@ahmed-sigmalux
Copy link

I'm running into this problem, too.

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