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

react-refresh-runtime.development.js:645 Uncaught ReferenceError: exports is not defined #62244

Open
xkeshav opened this issue Feb 19, 2024 · 3 comments
Labels
bug Issue was opened via the bug report template.

Comments

@xkeshav
Copy link

xkeshav commented Feb 19, 2024

Link to the code that reproduces this issue

https://github.com/xkeshav/reaction

To Reproduce

npm run dev

no issue on page but in console it gives issue

giving this issue which takes to this file

react-refresh-runtime.development.js:645 Uncaught ReferenceError: exports is not defined
line # 645 exports._getMountedRootCount = _getMountedRootCount

earliet it was having issue then runn npm install next@canary then it resolved but again this issue came

image

Current vs. Expected behavior

it should now give any issue in console.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.17.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

below info appears when run next info while i already run nthe command.

warn  - Latest canary version not detected, detected: "14.1.0", newest: "14.1.1-canary.61".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
@xkeshav xkeshav added the bug Issue was opened via the bug report template. label Feb 19, 2024
@Dal-Tron
Copy link

Can confirm I can see this same reference error

@alexcloudstar

This comment has been minimized.

@cbratschi
Copy link

Possibly linked to #61054

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

4 participants