6.x import signature about p-queue HOT 5 CLOSED

Does TypeScript have a compile target of esm?

Yes

If so, you could add a “module”: ‘dist/esm.js” or something and that would make this work transparently with esm users (who opt to bite the mjs bullet)

Not interested in compiling to multiple targets. I don't even think that's possible with TypeScript. I plan to switch everything over to ESM when it's out in Node.js without a flag. Until then, it's CJS. It's up to you to handle that.

In this case, it's seem more like a bug in the esm package though.

from p-queue.

As a workaround, this did the trick for me:

import pq from 'p-queue'
const PQueue = pq.default

However, I'm still a tad confused why this works and import { default as PQueue } from 'p-queue' does not.

from p-queue.

+1
import PQueue from 'p-queue' works in the Browser using parcel.js to build. But it does not work in Node.js
@jdhiro solution does work in Note, but is messy.

from p-queue.

import PQueue from 'p-queue' works in ts-node

from p-queue.

+1
import PQueue from 'p-queue' works in the Browser using parcel.js to build. But it does not work in Node.js
@jdhiro solution does work in Note, but is messy.

Same issue with Node, did you find a solution?

from p-queue.