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

Explanation about why it stopped to work suddenly since updating the last version of NextJs #9

Open
JesusDR01 opened this issue Sep 24, 2024 · 0 comments

Comments

@JesusDR01
Copy link

Hello, for those who are using the latest version of Next and the extension stopped working suddenly, here is the explanation:

The NextJs team have launched recently the 14.2.13 package, so everyone with

"next": "^14.1.0", in their package.json will face the extension suddenly stopped working (as it will be updated to a newer version by using ^)

Explanation about why this issue is happening:

NextJs team updated React right before 14.1.1-canary.45 version

image

This update, includes the commit facebook/react#28265

Comments from the author:
image

This commit is deleting _debugSource, here is the explanation of what is actually happening:

facebook/react#29092 (comment)

image

Using NextJs Version 14.1.1-canary.44 (before the ReactJs release):

image

Using NextJs Version 14.1.1-canary.45 (after the ReactJs release):

image

As the _debugSource is not there in the 14.1.1-canary.45 version, we cannot make use of the _debugSource to open the file in vscode.

NextJs developers who updated to the last version cannot make use of the extension till new updates on react fiber.

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

1 participant