Skip to content

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

@JesusDR01

Description

@JesusDR01

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions