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

Cannot create reproduction #65619

Closed
Vinnl opened this issue May 10, 2024 · 1 comment · Fixed by #65624
Closed

Cannot create reproduction #65619

Vinnl opened this issue May 10, 2024 · 1 comment · Fixed by #65624
Labels
bug Issue was opened via the bug report template. create-next-app Related to our CLI tool for quickly starting a new Next.js application. locked

Comments

@Vinnl
Copy link

Vinnl commented May 10, 2024

Link to the code that reproduces this issue

https://github.com/Vinnl/next-repro-csp-third-parties-bug

To Reproduce

  1. Run npx create-next-app -e reproduction-template
  2. Pick a name

Current vs. Expected behavior

Instead of the repo, I got:

Creating a new Next.js app in /tmp/custom-properties-reproduction.

Downloading files for example reproduction-template. This might take a moment.

Installing packages. This might take a couple of minutes.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"19.0.0-beta-4508873393-20240430" from next@14.3.0-canary.54
npm ERR! node_modules/next
npm ERR!   next@"canary" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sat Apr 27 17:53:31 UTC 2024
  Available memory (MB): 15695
  Available CPU cores: 8
Binaries:
  Node: 22.1.0
  npm: 10.7.0
  Yarn: 1.22.19
  pnpm: 8.14.2
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A

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

create-next-app

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

Other (Deployed)

Additional context

(Note that I linked to an older reproduction to avoid this issue getting closed.)

@Vinnl Vinnl added the bug Issue was opened via the bug report template. label May 10, 2024
@github-actions github-actions bot added the create-next-app Related to our CLI tool for quickly starting a new Next.js application. label May 10, 2024
ztanner added a commit that referenced this issue May 10, 2024
Our reproduction templates are pinned to `next@canary`. This updates to
use the correct `react` & `react-dom` dependencies since `canary` is
pointed to React 19.

Fixes #65619
panteliselef pushed a commit to panteliselef/next.js that referenced this issue May 20, 2024
Our reproduction templates are pinned to `next@canary`. This updates to
use the correct `react` & `react-dom` dependencies since `canary` is
pointed to React 19.

Fixes vercel#65619
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. create-next-app Related to our CLI tool for quickly starting a new Next.js application. locked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant