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

Head of develop will not build: corrupt tarballs and mysterious invalid version messages #767

Open
JohnThomson opened this issue Apr 4, 2023 · 1 comment

Comments

@JohnThomson
Copy link

This issue is a Bug

Expected Behaviour

I expect that following the instructions in the MD file, like this:
git clone --recursive -b develop https://github.com/readium/readium-js-viewer.git readium-js-viewer
cd readium-js-viewer
git checkout develop && git submodule foreach --recursive "git checkout develop"
npm run prepare:all

Will complete without fatal errors and result in a usable system that can be tested with npm run http.

Observed behaviour

Instead, I get the following errors: many warnings about deprecation, and then
npm WARN tarball tarball data for jquery-sizes@git+ssh://[email protected]/readium/jquery-sizes.git#d26d2510d069f84a64052c443a06b8534c5e9d0e (sha512-l2fcLLlCSYeWGPdGeWnadY/REi/qshKzwGwVvL89TGzDqh52vGZFgZPt7qeI2Clxq1c9EGuflWRtChS5HN4TMw==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for css-element-queries@git+ssh://[email protected]/readium/css-element-queries.git#ca32ace3aecb9e05fcfef0c6d3d33a4d2bde3312 (sha512-yv5N3bSzfwZu2NP3vgc9r6AbbbdOJHbm6GTw+Hds7HULlufIrKyuBIipAOBA+2VkJE65cKlhilRYAAgoKpy/yg==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for jquery-sizes@git+ssh://[email protected]/readium/jquery-sizes.git#d26d2510d069f84a64052c443a06b8534c5e9d0e (sha512-l2fcLLlCSYeWGPdGeWnadY/REi/qshKzwGwVvL89TGzDqh52vGZFgZPt7qeI2Clxq1c9EGuflWRtChS5HN4TMw==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for http-server@git+ssh://[email protected]/readium/http-server.git#9c6e56279af34381a5dae640b7d73762e8135bd7 (sha512-481V03ReScl/ZFWfdq9HLxAXX+puIjyZ2lqRZktQXA9LIY+QEx6ztl9U4xUgNlYE3WtU9rIIpFKH7WzAIjqYiA==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for css-element-queries@git+ssh://[email protected]/readium/css-element-queries.git#ca32ace3aecb9e05fcfef0c6d3d33a4d2bde3312 (sha512-yv5N3bSzfwZu2NP3vgc9r6AbbbdOJHbm6GTw+Hds7HULlufIrKyuBIipAOBA+2VkJE65cKlhilRYAAgoKpy/yg==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for http-server@git+ssh://[email protected]/readium/http-server.git#9c6e56279af34381a5dae640b7d73762e8135bd7 (sha512-481V03ReScl/ZFWfdq9HLxAXX+puIjyZ2lqRZktQXA9LIY+QEx6ztl9U4xUgNlYE3WtU9rIIpFKH7WzAIjqYiA==) seems to be corrupted. Trying again.
npm ERR! Invalid Version: 3.5.0pr2

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Thomson\AppData\Local\npm-cache_logs\2023-04-04T20_17_46_157Z-debug.log
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated [email protected]: This package is unmaintained and deprecated. See the GH Issue 259.
npm ERR! Invalid Version: 3.5.0pr2

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Thomson\AppData\Local\npm-cache_logs\2023-04-04T20_17_48_641Z-debug.log

Product

readium-js-viewer

Additional information

Working on Windows 11, in a bash shell in Visual Studio Code.
npm version 8.1.2
node version 16.13.1
commit 51f2aa0 of readium-js-viewer

The string 3.5.0pr2 is not found anywhere in the source tree, so I have no idea what npm is trying to get that version of or why.

I considered changing package.json to get a numbered version of jquery-sizes and http-server, but there is no indication I could find of even approximately what version might be needed.

Apologies for not reading your contribution guidelines. The link leads to a page with a further link that is broken (404).

I have attached the log mentioned in the error message.

2023-04-04T20_43_43_484Z-debug.log

@AaronCMuller
Copy link

This looks to be an issue with NPM that was fixed in version v8.13+. Simply upgrading will fix the issue.

See the following issue for further detail: npm/cli#4992

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

2 participants