-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng6 - Can't reexport the named export 'graphql' from non EcmaScript module #10744
Comments
For real world applications using graphql, this is a critical regression. Tried a few workarounds- forking and optimistically editing None worked. This is the only issue blocking Angular@6 migration for us |
@elmoGrummelig |
I upgraded to the freshly released
So it seems it is quite solved yet. Downgrading back graphql with |
Should work when next version after see graphql/graphql-js#1344 (comment) @PowerKiKi you need |
Works with |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
ng new fresh
cd fresh
npm i graphql@latest
app.module.ts
:npm start
Observed behavior
Desired behavior
Build should work
Mention any other details that might be useful (optional)
I don't know much about
.mjs
, but it appears it might be used instead of.js
in some cases: http://2ality.com/2017/05/es-module-specifiers.htmlIt appears this might be an issue of Webpack 4 configuration. See this for details.
The text was updated successfully, but these errors were encountered: