Open jacobgranberry opened 2 years ago
Any progress / workarounds regarding this issue? We have the same issue when we to update react-scripts to 5.0.0 for node 17 compatibility.
I have not unfortunately, seems like something that may have to be resolved on CRA's end, but the fact that they released 5.0 3 months ago and haven't had a single bug patch for it doesn't give me a lot of confidence in getting a fix anytime soon.
@awe79 any luck on your end resolving this?
@jacobgranberry nope we postponed the upgrade. Will take al look again in a couple of months.
Hi! Any update on that? I'm currently having the sames warnings with "aws-appsync": "^4.1.9"
@pauchena my advise would be to move away from the aws-appsync lib as much as possible since it also has poor/no support for hooks like useQuery and there does not seem to be much development.
Use only the 'aws-appsync-auth-link' to create the authlink and use that to make an ApolloLink for the ApolloClient
Do you want to request a feature or report a bug? Bug
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Install CRA5 with aws-appsync
What is the expected behavior? CRA5 should compile with no warnings
Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions?
Has anyone run into this issue or reconciled it somehow? Getting lots of warnings after upgrading
react-scripts
to version 5.0.0 which includes webpack 5. Everything compiles fine.Versions:
"aws-appsync": "^4.1.4", "graphql": "^15.7.0",
Sample of the warnings thrown, all rooted in the
aws-appsync
dependency: