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

NODE UPDATE: Yarn warnings #13

Open
dwbond opened this issue Nov 19, 2023 · 0 comments
Open

NODE UPDATE: Yarn warnings #13

dwbond opened this issue Nov 19, 2023 · 0 comments

Comments

@dwbond
Copy link
Collaborator

dwbond commented Nov 19, 2023

There are more yarn warnings than usual when running yarn dev with Node 18

warning [email protected]: 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 [email protected]: 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 [email protected]: request has been deprecated, see request/request#3142

warning [email protected]: 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 > [email protected]: 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant