Published target compatibility with webpack/rollup

The current publishing flow uses a tsconfig.json file (the one in src) and transpiles the module imports/exports to UMD.

When trying to bundle the vscode-css-languageservice npm package alongside monaco-editor-core, webpack errors about require being used in a way that cannot be staticly parsed.

Would you consider publishing to es2015 modules as well, and linking to that entry-point from the package.json’s “module” field?

To match with other solutions online, dist folder could be something in the form: dist/umd/... dist/esm/... etc.

The “module” field is being automatically picked by webpack, rollup, and other bundlers, and does not collide with the “main” field. It is only used during bundling.

[amir-arad]

possible workaround: matt-gadd/umd-compat-loader reverts the umd wrapping.

I’ve installed umd-compat-loader using npm and added the following to my webpack configuration (in module>rules):

{
    test: /node_modules\/vscode-/,
    use: {loader: "umd-compat-loader"}
}

and it seems to be working

[akosyakov]

Repositories which also cannot be consumed with webpack:

• https://github.com/Microsoft/vscode-uri
• https://github.com/Microsoft/node-jsonc-parser