Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Yarn package just broke #14

Closed
mr-bo-jangles opened this issue Mar 28, 2017 · 6 comments
Closed

Yarn package just broke #14

mr-bo-jangles opened this issue Mar 28, 2017 · 6 comments
Assignees
@armandabric
Labels
bug

Comments

@mr-bo-jangles
Copy link

mr-bo-jangles commented Mar 28, 2017 •
edited
Loading 

info No lockfile found.
warning prezola.com: No license field
[1/4] Resolving packages...
warning gulp > vinyl-fs > glob-stream > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning gulp > vinyl-fs > glob-watcher > gaze > globule > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning gulp > vinyl-fs > glob-watcher > gaze > globule > glob > [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. 28/03/2017, 11:08:08
warning browser-sync > localtunnel > request > [email protected]: Use uuid module instead
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/gulp-uglifycss/-/gulp-uglifycss-1.0.7.tgz: invalid tar file".
info If you think this is a bug, please open a bug report with the information provided in "/srv/src/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Removing intermediate container ab2294a90d76```
@poltro90
Copy link

poltro90 commented Mar 28, 2017 •
edited
Loading

Same issue applies to npm

npm install
npm ERR! tar.unpack untar error /Users/mb/.npm/gulp-uglifycss/1.0.7/package.tgz
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.4.1
npm ERR! npm  v2.14.20

npm ERR! invalid tar file

@mathieu-gilloots
Copy link

Here too

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs
Copy link

my npm install is broken too

@armandabric
Copy link
Member

I've publish a maintenance version yesterday (v1.0.7). I've used yarn publish to publish it. I think this could be an explanation of this.

I just publish a new version (v1.0.8) of the package using npm publish as before. Please tell me if this solve the issue.

armandabric referenced this issue Mar 29, 2017
@armandabric
v1.0.7
941811a
@armandabric
Copy link
Member

The problem of corrupted package seems to already be reported on yarn site: yarnpkg/yarn#2764 (comment)

Wait and see!

@armandabric armandabric self-assigned this Mar 29, 2017
@armandabric armandabric mentioned this issue Mar 29, 2017
Closed
@sweoggy
Copy link

sweoggy commented Mar 29, 2017

Hi @Spy-Seth, v1.0.8 works just fine over here where 1.0.7 did not, thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@armandabric armandabric

Labels
bug
Milestone
No milestone
Development

No branches or pull requests
6 participants
@armandabric @mr-bo-jangles @mathieu-gilloots @poltro90 @sweoggy @b6pzeusbc54tvhw5jgpyw8pwz2x6gs