ES Modules and `"moduleResolution":"NodeNext"` in v9 about luma.gl HOT 8 OPEN

https://github.com/visgl/deck.gl/blob/x/esm/tsconfig.module.json

from luma.gl.

Also -- the fix above should be fully backwards-compatible, so there's no problem with making that change in v9.1 instead of v9.0 if we prefer.

from luma.gl.

In loaders.gl we run a script call add-js-to-imports

#/bin/sh

echo '# Adding .js to import statements in dist folders'
find modules/*/dist -name "*.js" -exec sed -i '' "s/from '\.\(.*\)';/from '.\1.js';/" {} \;
find modules/*/dist -name "*.js" -exec sed -i '' "s/from '\.\(.*\)\.js\.js';/from '.\1';/" {} \;

from luma.gl.

That looks like a good solution to me, and definitely less churn than changing all source imports. Potentially then, we'd put something like that in each repository? It doesn't seem like that script is running in loaders.gl now, I don't see it called anywhere, and the suffixes are missing from published types –

https://unpkg.com/@loaders.gl/[email protected]/dist/index.d.ts

from luma.gl.

It seems this affects node16 module resolution in typescript, and not just nodenext. This section of the TS docs was helpful for me:

https://www.typescriptlang.org/docs/handbook/modules/reference.html#node16-nodenext-1

from luma.gl.

@Pessimistress

There is a need of adding explicit .js extensions to import statements in generated code as required by Node ESM?

Does the new ocular setup have a plugin to do this (I was assuming one of the plugins you used in the last PR did this), or do we need to add back post processing scripts?

from luma.gl.