Meteor npm import issue with relative paths

For example, when adding quill.js to a clean Meteor build, performing the basic import import results in:

I’ve had this come up a few times lately, I suspect the package may be trying to run something like

import { thing } from "quills/libraries"

and Meteor cannot support it. Or maybe it’s a feature in new versions of Node?

Curious if anyone has run into it, or if there is a solution?

You might be using the V1.3.7 which is published in the NPM. They also have a V2 beta which seems far ahead 1.3.7 (5 years after all). V2 seems to have no external dependencies so you might not have the ESM issue.

1 Like