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

spectaql 2.0.1 installation error #605

Closed
robinelvin opened this issue Dec 9, 2022 · 6 comments · Fixed by #606
Closed

spectaql 2.0.1 installation error #605

robinelvin opened this issue Dec 9, 2022 · 6 comments · Fixed by #606

Comments

@robinelvin
Copy link

robinelvin commented Dec 9, 2022

I'm trying to install for the first time:

yarn add -D spectacl

...prior output omitted for brevity

➤ YN0000: │ spectaql@npm:2.0.1 STDOUT
➤ YN0000: │ spectaql@npm:2.0.1 STDOUT > [email protected] build:vendor
➤ YN0000: │ spectaql@npm:2.0.1 STDOUT > node bin/build-vendor.mjs
➤ YN0000: │ spectaql@npm:2.0.1 STDOUT
➤ YN0000: │ spectaql@npm:2.0.1 STDERR No vendor-src directory. Not building vendor packages.
➤ YN0009: │ spectaql@npm:2.0.1 couldn't be built successfully (exit code 13, logs can be found here: /private/var/folders/p6/s92jvcdj1m37h71ygtl8cs_r0000gn/T/xfs-02057cca/build.log)
➤ YN0000: └ Completed in 5s 800ms
➤ YN0000: Failed with errors in 14s 863ms

Using Yarn 3.3.0 PnP on MacOS

While the package appears to be installed this error means my CI build fails.

EDIT: Whilst this fails on initial installation it only raises a warning when using yarn install --immutable

@newhouse newhouse mentioned this issue Dec 9, 2022
@newhouse
Copy link
Collaborator

newhouse commented Dec 9, 2022

Weird. Seems to be related to this: nodejs/node#40808

@newhouse
Copy link
Collaborator

newhouse commented Dec 9, 2022

Looks like you are using Yarn 3.3.0, but what version of Node are you on @robinelvin ?

@newhouse
Copy link
Collaborator

newhouse commented Dec 9, 2022

Can you clear things out and try things again with 2.0.2-beta.0 and let me know if that resolves the issue for you?

@robinelvin
Copy link
Author

Looks like you are using Yarn 3.3.0, but what version of Node are you on @robinelvin ?

Good catch.

node -v
v16.13.0

Can you clear things out and try things again with 2.0.2-beta.0 and let me know if that resolves the issue for you?

➤ YN0002: │ spectaql@npm:2.0.2-beta.0 doesn't provide jquery (p59002), requested by foundation-sites
➤ YN0002: │ spectaql@npm:2.0.2-beta.0 doesn't provide motion-ui (p2f3f8), requested by foundation-sites
➤ YN0002: │ spectaql@npm:2.0.2-beta.0 doesn't provide what-input (p8395b), requested by foundation-sites
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 1s 876ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ spectaql@npm:2.0.2-beta.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0019: │ spectaql-npm-2.0.1-466251f8f5-1023c13732.zip appears to be unused - removing
➤ YN0000: └ Completed in 1s 337ms
➤ YN0000: ┌ Link step
➤ YN0008: │ @elixirsoftware/core@workspace:. must be rebuilt because its dependency tree changed
➤ YN0007: │ spectaql@npm:2.0.2-beta.0 must be built because it never has been before or the last one failed
➤ YN0000: │ @elixirsoftware/core@workspace:. STDOUT husky - Git hooks installed
➤ YN0000: │ spectaql@npm:2.0.2-beta.0 STDOUT
➤ YN0000: │ spectaql@npm:2.0.2-beta.0 STDOUT > [email protected] build:vendor
➤ YN0000: │ spectaql@npm:2.0.2-beta.0 STDOUT > node bin/build-vendor.mjs
➤ YN0000: │ spectaql@npm:2.0.2-beta.0 STDOUT
➤ YN0000: │ spectaql@npm:2.0.2-beta.0 STDERR No vendor-src directory. Not building vendor packages.
➤ YN0000: └ Completed in 2s 489ms
➤ YN0000: Done with warnings in 6s 82ms

Seems better, thanks.

@robinelvin
Copy link
Author

robinelvin commented Dec 9, 2022

I've uninstalled and reinstalled to confirm and it appears to be happy now. Calling process.exit(0) looks like it fixes the problem.
Thanks

@newhouse
Copy link
Collaborator

newhouse commented Dec 9, 2022

Fix is out in 2.0.2. Thanks/sorry!

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

Successfully merging a pull request may close this issue.

2 participants