You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've been migrating our build system from webpack to esbuild, I am getting this error in build. I understand apollo-server-errors is not more in apolloServer v4, and we also don't use apolloServer v4, so is it safe for me to mark the path "apollo-server-errors" as external?
Thanks
✘ [ERROR] Could not resolve "apollo-server-errors"
You can mark the path "apollo-server-errors" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
The text was updated successfully, but these errors were encountered:
Hello, I've been migrating our build system from webpack to esbuild, I am getting this error in build. I understand
apollo-server-errors
is not more in apolloServer v4, and we also don't use apolloServer v4, so is it safe for me to mark the path "apollo-server-errors" as external?Thanks
✘ [ERROR] Could not resolve "apollo-server-errors"
You can mark the path "apollo-server-errors" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
The text was updated successfully, but these errors were encountered: