8000 Issues with hooks from a symlinked directory, integrated via workspaces (npm) · Issue #49097 · vercel/next.js · GitHub
[go: up one dir, main page]

Skip to content
Issues with hooks from a symlinked directory, integrated via workspaces (npm) #49097
@dominikzogg

Description

@dominikzogg

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Mon May  1 00:55:28 UTC 2023
    Binaries:
      Node: 18.16.0
      npm: 9.6.5
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.3.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

>=13.3.2

Link to the code that reproduces this issue

https://github.com/dominikzogg/reproduction-app

To Reproduce

Use my repo with master branch (next: >=13.3.2) and its broken, use the working-version branch 13.3.1 and it works.

Describe the Bug

When i upgrade next to >=13.3.2 it produces the following error:

../shared/hooks/use-cookie-consent.tsx (10:66) @ undefined
Unhandled Runtime Error
TypeError: dispatcher is null

It seems to work if its not symlinked (no issue on my build pipeline where files where copied to the shared folder within project directory.

I guess its related to: #48506

Expected Behavior

I expect that the code runs as it did until 13.3.1

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue was opened via the bug report template.lockedstaleThe issue has not seen recent activity.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0