rsnext/packages
Phil Wolstenholme e93a35bb26
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
```
2023-10-26 22:05:01 +00:00
..
create-next-app v14.0.0 2023-10-26 16:04:54 +00:00
eslint-config-next v14.0.0 2023-10-26 16:04:54 +00:00
eslint-plugin-next v14.0.0 2023-10-26 16:04:54 +00:00
font v14.0.0 2023-10-26 16:04:54 +00:00
next v14.0.0 2023-10-26 16:04:54 +00:00
next-bundle-analyzer v14.0.0 2023-10-26 16:04:54 +00:00
next-codemod v14.0.0 2023-10-26 16:04:54 +00:00
next-env v14.0.0 2023-10-26 16:04:54 +00:00
next-mdx v14.0.0 2023-10-26 16:04:54 +00:00
next-plugin-storybook v14.0.0 2023-10-26 16:04:54 +00:00
next-polyfill-module v14.0.0 2023-10-26 16:04:54 +00:00
next-polyfill-nomodule v14.0.0 2023-10-26 16:04:54 +00:00
next-swc v14.0.0 2023-10-26 16:04:54 +00:00
react-dev-overlay v14.0.0 2023-10-26 16:04:54 +00:00
react-refresh-utils v14.0.0 2023-10-26 16:04:54 +00:00
third-parties update next/third-parties to use Next 14 or 13 as a peer dependency, instead of just 13 (#57515) 2023-10-26 22:05:01 +00:00