There are more yarn warnings than usual when running yarn dev with Node 18
warning apollo-server-express@1.4.0: The apollo-server-express package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
Will need to investigate how this package is used
warning graphql-tools@2.24.0: This package has been deprecated and now it only exports makeExecutableSchema. And it will no longer receive updates. We recommend you to migrate to scoped packages such as @graphql-tools/schema, @graphql-tools/utils and etc. Check out https://www.graphql-tools.com to learn what package you should use instead
warning json2csv@3.11.5: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
outright deprecations, some suggest replacement, others may require research
Remaining have unmet peer dependencies or incorrect peer dependencies, suggesting that there shouldn't be anything wrong per se, but the package json file didn't smoothly transition these specific packages along
There are two related warnings that will require a similar package json file tweak to resolve
"optionalDependencies" has dependency "webpack-cli" with range "^4.7.2" that collides with a dependency in "devDependencies" of the same name with version "^4.10.0"
This seems like it was edited at two different points, so should go clean up the 4.7.2 reference
warning webpack-dev-server > chokidar > fsevents@1.2.13: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
Update the version number in the package json file... your guess is as good as mine as to why it doesn't do this automatically if the version is known to be unsafe, and can be safely upgraded
There are more yarn warnings than usual when running
yarn devwith Node 18Will need to investigate how this package is used
outright deprecations, some suggest replacement, others may require research
Remaining have unmet peer dependencies or incorrect peer dependencies, suggesting that there shouldn't be anything wrong per se, but the package json file didn't smoothly transition these specific packages along
There are two related warnings that will require a similar package json file tweak to resolve
This seems like it was edited at two different points, so should go clean up the 4.7.2 reference
Update the version number in the package json file... your guess is as good as mine as to why it doesn't do this automatically if the version is known to be unsafe, and can be safely upgraded