-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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
NODE_OPTIONS=--inspect
won't work properly after version 13.2.0
#46948
Labels
bug
Issue was opened via the bug report template.
Comments
11 tasks
and I've submit a pr for this #46757 |
11 tasks
ijjk
pushed a commit
that referenced
this issue
Mar 9, 2023
<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: --> ## Bug fix #46948 - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by: Seiry Yu <seiry@squareup.com>
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Verify canary release
Provide environment information
npx next info Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000 Binaries: Node: 16.14.0 npm: 8.3.1 Yarn: 1.22.17 pnpm: 6.32.3 Relevant packages: next: 13.2.4-canary.8 eslint-config-next: 13.2.3 react: 18.2.0 react-dom: 18.2.0
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue
https://github.com/seiry/inspect-bug
To Reproduce
init a repo using
npx create-next-app
, and change script inpackage.json
to use chrome inspect debugger"dev": "NODE_OPTIONS=--inspect next dev",
, and runnpm run dev
Describe the Bug
the debugger wont work like before
![image](https://user-images.githubusercontent.com/4397354/223912603-e840f4e9-3c08-4e82-a475-7e3a270d2bb0.png)
and error msg:
![image](https://user-images.githubusercontent.com/4397354/223911211-cc7869f8-137e-4e99-94a3-ac811004b96a.png)
maybe this pr caused the bug:
#45745
https://github.com/vercel/next.js/pull/45745/files#diff-ddadbe5e107283e1bda7713050b8dcc19065dc804ab082e55e148efac0ef0221R443
![image](https://user-images.githubusercontent.com/4397354/223913916-fa411b86-ca2d-45ac-a9f7-ec54784856b3.png)
for the --inspect flag is deprecatedExpected Behavior
should be a node js server code debugger
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: