Unverified Commit e93a35bb authored by Phil Wolstenholme's avatar Phil Wolstenholme Committed by GitHub

update next/third-parties to use Next 14 or 13 as a peer dependency, instead of just 13 (#57515)

Just tried to update to 14 but `next/third-parties` looks like it's still expecting us to be on Next 13

```
Error: npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: shop-next@0.1.1
npm ERR! Found: next@14.0.0
npm ERR! node_modules/next
npm ERR!   next@"^14.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^13.0.0" from @next/third-parties@14.0.0
npm ERR! node_modules/@next/third-parties
npm ERR!   @next/third-parties@"^14.0.0" 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.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /Users/XXXXXXXX/.npm/_logs/2023-10-26T17_27_38_736Z-eresolve-report.txt
```
parent 27bfd2d2
...@@ -27,7 +27,7 @@ ...@@ -27,7 +27,7 @@
"prettier": "2.5.1" "prettier": "2.5.1"
}, },
"peerDependencies": { "peerDependencies": {
"next": "^13.0.0", "next": "^13.0.0 || ^14.0.0",
"react": "^18.2.0" "react": "^18.2.0"
} }
} }
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment