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

Package "unexpected end of file" #16

Closed
colbyfayock opened this issue Sep 3, 2019 · 4 comments
Closed

Package "unexpected end of file" #16

colbyfayock opened this issue Sep 3, 2019 · 4 comments

Comments

@colbyfayock
Copy link

colbyfayock commented Sep 3, 2019

Hey there,

I'm using bump both locally and on our Jenkins build process and I keep running into an issue where I get an unexpected end of file error on the bump package on version 1.2.2.

image

Similarly, if you try to download that file manually in your browser, you get a Failed - Network Error: https://registry.yarnpkg.com/@fabiospampinato/bump/-/bump-1.2.2.tgz

image

Wondering if anyone else has ran into this before. Unsure if there's an issue with the package or if it's for some reason a Yarn issue.

Using yarn v1.17.3

I downgraded to 1.2.1 so far anddd so far so good (knock on wood). Maybe it's a corrupt package in the registry?

Thanks

@colbyfayock
Copy link
Author

Found this also on the yarn repo: yarnpkg/yarn#4412

May be a content-length header issue? though unsure if it's a package issue.

@colbyfayock
Copy link
Author

Update: 1.2.1 started to give me the issue as well. Wondering if this is a yarn issue, however, i haven't experienced this on any other packages 🤷‍♂

@barakd
Copy link

barakd commented Sep 3, 2019

I started experiencing this issue as well, using yarn v1.17.3
usually it's solving itself when running yarn install the second time, although while reasonable on developer machines it very problematic on the CI.
I noticed it's happening only when proxying packages from our private npm registry (hosted on private npm)

@fabiospampinato
Copy link
Owner

I've just tried downloading the package manually as well as installing it via yarn and it works for me, in any case I don't think this is an issue with bump itself, I don't think there's anything I can do to fix it 🤷‍♂

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