Can't reexport the named export from non EcmaScript module (only default export is available)

Question

Can't reexport the named export from non EcmaScript module (only default export is available)

frederikhors opened this issue 6 years ago · comments

frederikhors commented 6 years ago

I'm trying vue.js and vue-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:

ERROR  Failed to compile with 175 errors
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'BREAK' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'BreakingChangeType' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'DEFAULT_DEPRECATION_REASON' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'DangerousChangeType' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'DirectiveLocation' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'FieldsOnCorrectTypeRule' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
Can't reexport the named export 'FragmentsOnCompositeTypesRule' from non EcmaScript module (only default export is available)
error  in ./node_modules/graphql/index.mjs
...

If I switch to 0.4.1 everything works as expected.

Are you already aware of it?

Maybe related to these:

#301
#298

Thomas Ramé commented 6 years ago

Up?

Scott · Answer 1 · Wed Oct 10 2018 03:10:59 GMT+0800 (China Standard Time)

I just ran into this issue too. Using 0.4.1 fixed it.

Scott

Lucas · Answer 2 · Wed Oct 17 2018 07:34:59 GMT+0800 (China Standard Time)

I am running into this problem as well, not even using 0.4.1 fixed it!

Scott · Answer 3 · Wed Oct 17 2018 11:51:00 GMT+0800 (China Standard Time)

@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

Tim Mikeladze · Answer 4 · Thu Oct 18 2018 07:00:33 GMT+0800 (China Standard Time)

Perhaps adding the following to your webpack config can help graphql/graphql-js#1272 (comment)

Lucas · Answer 5 · Fri Oct 19 2018 09:53:04 GMT+0800 (China Standard Time)

Yep.!

Just add this to vue.config.js!

const config = {
 configureWebpack: {
   resolve: {
     // .mjs needed for https://github.com/graphql/graphql-js/issues/1272
     extensions: ['*', '.mjs', '.js', '.vue', '.json', '.gql', '.graphql']
   },
   module: {
     rules: [ // fixes https://github.com/graphql/graphql-js/issues/1272
       {
         test: /\.mjs$/,
         include: /node_modules/,
         type: 'javascript/auto'
       }
     ]
   }
 }
}

module.exports = config

Scott · Answer 6 · Fri Oct 19 2018 13:26:31 GMT+0800 (China Standard Time)

@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

Lucas · Answer 7 · Fri Oct 19 2018 13:27:40 GMT+0800 (China Standard Time)

@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.

Scott · Answer 8 · Fri Oct 19 2018 13:28:25 GMT+0800 (China Standard Time)

That's what I thought, but wasn't certain. Appreciate the help!

Scott

Angelo Michel · Answer 9 · Mon Oct 29 2018 22:54:14 GMT+0800 (China Standard Time)

edit: it is resolved now (the order of the extensions seemed to be important too, mine are also first "mjs" now)

blocka · Answer 10 · Mon Dec 17 2018 17:59:10 GMT+0800 (China Standard Time)

Using vue-cli 3:
this helped for me

    config.module
      .rule('mjs')
      .test(/\.mjs$/)
      .type('javascript/auto')
      .end()

Onuwa Nnachi Isaac · Answer 11 · Fri Mar 08 2019 20:52:32 GMT+0800 (China Standard Time)

Yep.!

Just add this to vue.config.js!

const config = {
 configureWebpack: {
   resolve: {
     // .mjs needed for https://github.com/graphql/graphql-js/issues/1272
     extensions: ['*', '.mjs', '.js', '.vue', '.json', '.gql', '.graphql']
   },
   module: {
     rules: [ // fixes https://github.com/graphql/graphql-js/issues/1272
       {
         test: /\.mjs$/,
         include: /node_modules/,
         type: 'javascript/auto'
       }
     ]
   }
 }
}

module.exports = config

This is the solution @romucci thank you

Onuwa Nnachi Isaac · Answer 12 · Fri Mar 08 2019 20:53:05 GMT+0800 (China Standard Time)

Using vue-cli 3:
this helped for me

    config.module
      .rule('mjs')
      .test(/\.mjs$/)
      .type('javascript/auto')
      .end()

Could do it. But requires the node_modules directory