Skip to content

Sergical/fix nextjs console check #16061

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

Closed

Conversation

sergical
Copy link

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

  • If you've added code that should be tested, please add tests.
  • Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

Would like to avoid

> next dev --turbopack

[@sentry/nextjs] WARNING: You are using the Sentry SDK with Turbopack (`next dev --turbo`). The Sentry SDK is compatible with Turbopack on Next.js version 15.3.0 or later. You are currently on 15.3.0. Please upgrade to a newer Next.js version to use the Sentry SDK with Turbopack. Note that the SDK will continue to work for non-Turbopack production builds. This warning is only about dev-mode.
   ▲ Next.js 15.3.0 (Turbopack)

@Lms24 Lms24 requested a review from lforst April 15, 2025 08:55
@lforst
Copy link
Member

lforst commented Apr 15, 2025

This logic is quite intentional. What exact Next.js version do you have in your package.json?

@sergical
Copy link
Author

This logic is quite intentional. What exact Next.js version do you have in your package.json?

15.3.0

@lforst
Copy link
Member

lforst commented Apr 15, 2025

Have you tested the change locally?

@sergical
Copy link
Author

Have you tested the change locally?

building locally right now - there's no way to not have to build directly from the root, just do all the ones that are necessary for the nextjs one?

@sergical
Copy link
Author

having a hard time building locally 😓 building types is taking a very long time before i am able to build the nextjs package

@lforst
Copy link
Member

lforst commented Apr 16, 2025

This is already fixed by #16026 👍

@lforst lforst closed this Apr 16, 2025
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 this pull request may close these issues.

2 participants