SyntaxError: import not found: EventEmitter

[gweiermann]

Hi :)
I just installed "events" using npm and tried to use it. VisualStudioCode is totally fine with it, but with snowpack I get a RuntimeError.
This code here:

import { EventEmitter } from 'events';

class Foo extends EventEmitter {

}

throws this error:

Unhandled Runtime Error

SyntaxError: import not found: EventEmitter

Am I using "events" wrong or is that a bug of snowpack?

[FredKSchott]

Great find! There are a few older npm packages like this that can't be scanned properly for ESM conversion, so they only expose a default export. In this case, you need to do:

import events from 'events';
const {EventEmitter} = events;

But I'll go ahead and add this package to a list that we keep internally in Snowpack. In the next release, your code snippet above should work.

977621d

[gweiermann]

Alright, thank you so much!
I tried similar attempts, but this finally worked :)

Have a good day :D

[feugy]

Hey, for the record, I had the same issue with Babylon.js, and your trick fixed it.

import Babylon from 'babylonjs'
const { Engine, Scene } = Babylon

Thanks again for the tip!

[feugy]

Babylonjs is actually has ESM bindings: it's as simple as importing @babylonjs/core with npm/yarn

[PixsaOJ]

When I did this, it finally worked! But now objects are missing many properties.

e.g:

const { Bodies, Body, Engine, World } = Matter;

let engine: typeof Engine;

Typescript gives warnings:

Type 'Engine' is missing the following properties from type 'typeof Engine': prototype, clear, create, merge, and 2 more.ts(2740)
let engine: typeof Matter.Engine

[PixsaOJ]

Update: Here is how I fixed it:

import Matter, {
    Body as BodyType,
    Engine as EngineType,
    World as WorldType
} from 'matter-js';
const { Bodies, Engine, World } = Matter;


let engine: EngineType;

So, I am importing them twice, first time as types and second time as actual modules. This does not look good to me at all. However, no errors ay?