-
Notifications
You must be signed in to change notification settings - Fork 100
Can't reexport the named export from non EcmaScript module (only default export is available) #302
Comments
Up? |
I just ran into this issue too. Using 0.4.1 fixed it. Scott |
I am running into this problem as well, not even using 0.4.1 fixed it! |
@peggyrayzis - Can you have a look at this please? I want to write an article about using apollo-link-state, but I don't want to have to tell everyone they can't use the latest version. That would be sort of ridiculous. Scott |
Perhaps adding the following to your webpack config can help graphql/graphql-js#1272 (comment) |
Yep.! Just add this to vue.config.js!
|
@romucci @TimMikeladze - Thanks. That solution fixed it for me too. Is this "the" fix? Or is does the Apollo team still need to look at this? Scott |
It shouldn't be THE fix. |
That's what I thought, but wasn't certain. Appreciate the help! Scott |
edit: it is resolved now (the order of the extensions seemed to be important too, mine are also first "mjs" now) |
Using vue-cli 3: config.module
.rule('mjs')
.test(/\.mjs$/)
.type('javascript/auto')
.end() |
This is the solution @romucci thank you |
Could do it. But requires the node_modules directory |
I'm trying
vue.js
andvue-cli
(which uses webpack 4 I think).I'm adding
"apollo-link-state": "0.4.2"
to the project and when I import something like this:import { withClientState } from 'apollo-link-state'
and start with
npm run serve
I'm having hundreds of errors like below:If I switch to
0.4.1
everything works as expected.Are you already aware of it?
Maybe related to these:
The text was updated successfully, but these errors were encountered: