Mojtaba Samimi

It's coming from ```js let supportsOffscreenCanvas; function offscreenCanvasSupported() { if (supportsOffscreenCanvas == null) { supportsOffscreenCanvas = typeof OffscreenCanvas !== 'undefined' && new OffscreenCanvas(1, 1).getContext('2d') && typeof createImageBitmap === 'function'; }...

Until we publish `plotly.js-map-dist` packages similar to https://www.npmjs.com/package/plotly.js-mapbox-dist, to create a custom bundle including maplibre traces, one could run ```sh npm run custom-bundle -- --unminified --traces choroplethmap,densitymap,scattermap ``` But strangely...

Oops. It actually did throw an error with the modified script for custom `map` bundle. So it could be something you may fix at maplibre level.

Here is a faster command for testing: ```sh npm run custom-bundle -- --unminified --traces scattermap && node ./node_modules/eslint/bin/eslint.js --no-ignore --no-eslintrc --no-inline-config --rule '{no-new-func: warn}' dist/plotly-custom.js ```

Thanks @birkskyum for the note. I think the fix should be in plotly.js/webpack.config.js not on the maplibre. We already have es6 dependencies similar to maplibre.

Which version of node and npm you are on?