ECMAScript module loading error about graphql-upload HOT 8 CLOSED

I started the program also with node --experimental-modules ./server.mjs and @std/esm, but no success. The same without @std/esm. Only the error message is more informative. I found no solution other than import by default and destructuring the imported default object. Thank you for your help.

from graphql-upload.

Ok, maybe you can use a temporary solution with a mix of default and variable import like this one:
import myDefault, * as myModule from "my-module";
Not sure if it works for both, vanilla Node and Babel.

And then you can add a conditional assignment like that:
const graphql = myDefault || myModule

from graphql-upload.

Now, it works - thanks 👍

from graphql-upload.

I was using vanilla --experimental-modules, but have recently been using @std/esm in cjs mode so it's possible this slipped under the radar. The intent is to be 100% vanilla .mjs compatible. Looking into it now…

from graphql-upload.

Hang on, the fix is not working 😱

from graphql-upload.

The issue is that this in the source works correctly for .mjs, but breaks in the .js:

import graphql from 'graphql'
export const GraphQLUpload = new graphql.GraphQLScalarType({ … })

While this breaks the .mjs but works for the .js:

import * as graphql from 'graphql'
export const GraphQLUpload = new graphql.GraphQLScalarType({ … })

Not sure if it is a Babel bug or what.

from graphql-upload.

Related? babel/babel#6983

from graphql-upload.

This should be fixed in v4.0.2. I'll continue to investigate a better solution.

I've updated the example API to use native modules instead of @std/esm.

from graphql-upload.