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

Unable to install @sentry/nextjs package #6579

Closed
3 tasks done
ajaykarthikr opened this issue Dec 19, 2022 · 7 comments
Closed
3 tasks done

Unable to install @sentry/nextjs package #6579

ajaykarthikr opened this issue Dec 19, 2022 · 7 comments

Comments

@ajaykarthikr
Copy link

ajaykarthikr commented Dec 19, 2022

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/nextjs

SDK Version

7.27.0

Framework Version

React 17.0.2, Next 12.2.5

Link to Sentry event

No response

Steps to Reproduce

Unable to install latest version @sentry/nextjs package in WSL Ubuntu 20.

npm install @sentry/nextjs@latest

Expected Result

This should have installed sentry package for nextjs

Actual Result

Error Log

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'openid-client@5.1.4',
npm WARN EBADENGINE   required: { node: '^12.19.0 || ^14.15.0 || ^16.13.0' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm ERR! code 1
npm ERR! path /home/username/projects/test-project/node_modules/@sentry/cli
npm ERR! command failed
npm ERR! command sh -c node ./scripts/install.js
npm ERR! fetching sentry-cli-Linux-x86_64 1%
npm ERR! fetching sentry-cli-Linux-x86_64 2%
npm ERR! fetching sentry-cli-Linux-x86_64 3%
npm ERR! fetching sentry-cli-Linux-x86_64 4%
npm ERR! fetching sentry-cli-Linux-x86_64 5%
npm ERR! fetching sentry-cli-Linux-x86_64 6%
npm ERR! fetching sentry-cli-Linux-x86_64 7%
npm ERR! fetching sentry-cli-Linux-x86_64 8%
npm ERR! fetching sentry-cli-Linux-x86_64 9%
npm ERR! fetching sentry-cli-Linux-x86_64 10%
npm ERR! fetching sentry-cli-Linux-x86_64 11%
npm ERR! fetching sentry-cli-Linux-x86_64 12%
npm ERR! fetching sentry-cli-Linux-x86_64 13%
npm ERR! fetching sentry-cli-Linux-x86_64 14%
npm ERR! fetching sentry-cli-Linux-x86_64 15%
npm ERR! fetching sentry-cli-Linux-x86_64 16%
npm ERR! fetching sentry-cli-Linux-x86_64 17%
npm ERR! fetching sentry-cli-Linux-x86_64 18%
npm ERR! fetching sentry-cli-Linux-x86_64 19%
npm ERR! fetching sentry-cli-Linux-x86_64 20%
npm ERR! fetching sentry-cli-Linux-x86_64 21%
npm ERR! fetching sentry-cli-Linux-x86_64 22%
npm ERR! fetching sentry-cli-Linux-x86_64 23%
npm ERR! fetching sentry-cli-Linux-x86_64 24%
npm ERR! fetching sentry-cli-Linux-x86_64 25%
npm ERR! fetching sentry-cli-Linux-x86_64 26%
npm ERR! fetching sentry-cli-Linux-x86_64 27%
npm ERR! fetching sentry-cli-Linux-x86_64 28%
npm ERR! fetching sentry-cli-Linux-x86_64 29%
npm ERR! fetching sentry-cli-Linux-x86_64 30%
npm ERR! fetching sentry-cli-Linux-x86_64 31%
npm ERR! fetching sentry-cli-Linux-x86_64 32%
npm ERR! fetching sentry-cli-Linux-x86_64 33%
npm ERR! fetching sentry-cli-Linux-x86_64 34%
npm ERR! fetching sentry-cli-Linux-x86_64 35%
npm ERR! fetching sentry-cli-Linux-x86_64 36%
npm ERR! fetching sentry-cli-Linux-x86_64 37%
npm ERR! fetching sentry-cli-Linux-x86_64 38%
npm ERR! fetching sentry-cli-Linux-x86_64 39%
npm ERR! fetching sentry-cli-Linux-x86_64 40%
npm ERR! fetching sentry-cli-Linux-x86_64 41%
npm ERR! fetching sentry-cli-Linux-x86_64 42%
npm ERR! fetching sentry-cli-Linux-x86_64 43%
npm ERR! fetching sentry-cli-Linux-x86_64 44%
npm ERR! fetching sentry-cli-Linux-x86_64 45%
npm ERR! fetching sentry-cli-Linux-x86_64 46%
npm ERR! fetching sentry-cli-Linux-x86_64 47%
npm ERR! fetching sentry-cli-Linux-x86_64 48%
npm ERR! fetching sentry-cli-Linux-x86_64 49%
npm ERR! fetching sentry-cli-Linux-x86_64 50%
npm ERR! fetching sentry-cli-Linux-x86_64 51%
npm ERR! fetching sentry-cli-Linux-x86_64 52%
npm ERR! fetching sentry-cli-Linux-x86_64 53%
npm ERR! fetching sentry-cli-Linux-x86_64 54%
npm ERR! fetching sentry-cli-Linux-x86_64 55%
npm ERR! fetching sentry-cli-Linux-x86_64 56%
npm ERR! fetching sentry-cli-Linux-x86_64 57%
npm ERR! fetching sentry-cli-Linux-x86_64 58%
npm ERR! fetching sentry-cli-Linux-x86_64 59%
npm ERR! fetching sentry-cli-Linux-x86_64 60%
npm ERR! fetching sentry-cli-Linux-x86_64 61%
npm ERR! fetching sentry-cli-Linux-x86_64 62%
npm ERR! fetching sentry-cli-Linux-x86_64 63%
npm ERR! fetching sentry-cli-Linux-x86_64 64%
npm ERR! fetching sentry-cli-Linux-x86_64 65%
npm ERR! fetching sentry-cli-Linux-x86_64 66%
npm ERR! fetching sentry-cli-Linux-x86_64 67%
npm ERR! fetching sentry-cli-Linux-x86_64 68%
npm ERR! fetching sentry-cli-Linux-x86_64 69%
npm ERR! fetching sentry-cli-Linux-x86_64 70%
npm ERR! fetching sentry-cli-Linux-x86_64 71%
npm ERR! fetching sentry-cli-Linux-x86_64 72%
npm ERR! fetching sentry-cli-Linux-x86_64 73%
npm ERR! fetching sentry-cli-Linux-x86_64 74%
npm ERR! fetching sentry-cli-Linux-x86_64 75%
npm ERR! fetching sentry-cli-Linux-x86_64 76%
npm ERR! fetching sentry-cli-Linux-x86_64 77%
npm ERR! fetching sentry-cli-Linux-x86_64 78%
npm ERR! fetching sentry-cli-Linux-x86_64 79%
npm ERR! fetching sentry-cli-Linux-x86_64 80%
npm ERR! fetching sentry-cli-Linux-x86_64 81%
npm ERR! fetching sentry-cli-Linux-x86_64 82%
npm ERR! fetching sentry-cli-Linux-x86_64 83%
npm ERR! fetching sentry-cli-Linux-x86_64 84%
npm ERR! fetching sentry-cli-Linux-x86_64 85%
npm ERR! fetching sentry-cli-Linux-x86_64 86%
npm ERR! fetching sentry-cli-Linux-x86_64 87%
npm ERR! fetching sentry-cli-Linux-x86_64 88%
npm ERR! fetching sentry-cli-Linux-x86_64 89%
npm ERR! fetching sentry-cli-Linux-x86_64 90%
npm ERR! fetching sentry-cli-Linux-x86_64 91%
npm ERR! fetching sentry-cli-Linux-x86_64 92%
npm ERR! fetching sentry-cli-Linux-x86_64 93%
npm ERR! fetching sentry-cli-Linux-x86_64 94%
npm ERR! fetching sentry-cli-Linux-x86_64 95%
npm ERR! fetching sentry-cli-Linux-x86_64 96%
npm ERR! fetching sentry-cli-Linux-x86_64 97%
npm ERR! fetching sentry-cli-Linux-x86_64 98%
npm ERR! fetching sentry-cli-Linux-x86_64 99%
npm ERR! fetching sentry-cli-Linux-x86_64 100%
npm ERR! info sentry-cli Downloading from https://downloads.sentry-cdn.com/sentry-cli/1.74.6/sentry-cli-Linux-x86_64
npm ERR! info Checksum validation passed. 
npm ERR! Error: Command failed: /home/username/projects/test-project/node_modules/@sentry/cli/sentry-cli --version
npm ERR! error: 0:7 doesn't support inline comment
npm ERR! thread 'unnamed' panicked at 'Config not bound yet': src/config.rs:87
npm ERR! 
npm ERR!    0: backtrace::backtrace::trace

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/username/.npm/_logs/2022-12-19T13_20_31_113Z-debug-0.log

Also, I'm receiving the same error in Vercel.

@Lms24
Copy link
Member

Lms24 commented Dec 19, 2022

Hi @ajaykarthikr this might be related to getsentry/sentry-cli#1317 or to openid-client requiring node 16 but this project being built in node 18. Not entirely sure but overall this seems to be CLI-compatibility related rather than a NextJS SDK issue.

Gonna tag @kamilogorek for some more context around CLI compatibility. Is there something we can do here?

@ajaykarthikr
Copy link
Author

Hi @Lms24, I went through the thread and couldn't find a solution.
I ran the downloaded executable directly and it works but it doesn't work via npm install. I think this is some symlink issue.

username@ubuntu-20:~/.npm/sentry-cli$ ./cfa322-sentry-cli-Linux-x86-64  --version
sentry-cli 1.74.6

@ajaykarthikr
Copy link
Author

Hey @Lms24 @kamilogorek any update? Installation is still failing in vercel deployments.

@kamilogorek
Copy link
Contributor

I'm also quite lost here, not a clue what this deployment is doing there.
We've not received a similar issue from people deploying to Vercel in the past, and tbh v1 is in the security-fixes mode only.
v2 already has support for node >=10, so we should just bump webpack plugin to use it instead of trying to fix old major.

Issue is tracked here getsentry/sentry-webpack-plugin#383

Oooor use https://github.com/getsentry/sentry-javascript-bundler-plugins whenever suitable.

@github-actions
Copy link
Contributor

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@ajaykarthikr
Copy link
Author

Sure, will try it. Thanks for the help.

@github-actions
Copy link
Contributor

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants