-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Error: Cannot find module 'core-js/modules/es7.object.entries' #1542
Comments
official getting-started example shows the same error. https://www.apollographql.com/docs/apollo-server/getting-started.html |
I am having the same problem using apollo-server-express. The issue seems to be caused by the peer dependency |
A temporary workaround : |
…ependency. As reported in #1542, the `apollo-upload-server` package (v5.0.0, which `apollo-server` relies on) is no longer able to provide a `core-js` package because of change that was outside of its control in a Babel release. The problem is resolved in newer versions of `apollo-upload-server`, however, regrettably, the newer versions of that package (notably, v6 and v7) drop support for Node.js 6 — one of two versions of Node.js that are currently under the terms of the Node.js Foundation's Long-Term-Support (LTS) agreements. Since Apollo Server aims to support versions of Node.js which are under LTS (and will drop support for Node.js 6 in April 2019, per Node.js' schedule) the current, immediate solution is to fork the `apollo-upload-server` package as `@apollographql/apollo-upload-server`. With the inclusion of https://github.com/apollographql/apollo-upload-server/pull/1, we are able to keep supporting Node.js 6. Without this change, every new installation of `apollo-server`, which doesn't have a `package-lock.json` preventing transitive dependency updates - specifically, the updates to `@babel/runtime` versions newer than `-beta.56` - is broken.
…ependency. (#1556) * Switch to a fork of `apollo-upload-server` to fix missing `core-js` dependency. As reported in #1542, the `apollo-upload-server` package (v5.0.0, which `apollo-server` relies on) is no longer able to provide a `core-js` package because of change that was outside of its control in a Babel release. The problem is resolved in newer versions of `apollo-upload-server`, however, regrettably, the newer versions of that package (notably, v6 and v7) drop support for Node.js 6 — one of two versions of Node.js that are currently under the terms of the Node.js Foundation's Long-Term-Support (LTS) agreements. Since Apollo Server aims to support versions of Node.js which are under LTS (and will drop support for Node.js 6 in April 2019, per Node.js' schedule) the current, immediate solution is to fork the `apollo-upload-server` package as `@apollographql/apollo-upload-server`. With the inclusion of https://github.com/apollographql/apollo-upload-server/pull/1, we are able to keep supporting Node.js 6. Without this change, every new installation of `apollo-server`, which doesn't have a `package-lock.json` preventing transitive dependency updates - specifically, the updates to `@babel/runtime` versions newer than `-beta.56` - is broken. * [squash] Update to `@apollographql/apollo-upload-server@5.0.2`. * [squash] Update to `@apollographql/apollo-upload-server@5.0.3`.
This is now fixed in Therefore, if you've previously installed Thanks for reporting this originally! |
hmm |
@abenhamdine Sorry, you're right, I should have just said "it's fixed in |
This is still not fixed for |
@Human-a The official release of That is to say, can you try with |
Awesome! thanks :) |
After upgrading to 2.3.3, I got the same error again. Downgrading to 2.0.4 fixed it. |
Same here 😞 |
Same here but with following error: |
I'm using apollo-server-express 2.2.6 and yarn install, any idea about how to solve this? I have another project with same base code and package version and it is working! |
@giovangonzalez Please update to a newer version of Apollo Server and see if the problem is still occurring. If it is, please open a new issue with a runnable reproduction, per the instructions when opening a new issue. Thanks! |
I am trying to serve an executable schema. I get the following error while using version
2.0.2
. Works totally fine with version2.0.0
.Here is the code:
/label bug
The text was updated successfully, but these errors were encountered: