Reconsider hidden-source-map

[skrat]

So when one is developing an npm/webpack project and using fengari-web, it is hard to debug anything that comes from fengari. And even though there is a source map, there's no way for my webpack project to expose that to the browser, because fengari-web is using the odd hidden-source-map devtool in its webpack config. This prevents any debugging in the browser.

That said, could you please consider using source-map instead? The part that is missing is the reference to the source map from the bundled JS blob. From webpack's docs:

hidden-source-map - Same as source-map, but doesn't add a reference comment to the bundle. Useful if you only want SourceMaps to map error stack traces from error reports, but don't want to expose your SourceMap for the browser development tools.

[daurnimator]

hidden-source-map was chosen because there is no assumption of the path where fengari-web is served from or what other files are present on the server.
If you want to use a different devtool then you should be able to select that yourself?

[skrat]

The client project can't re-attach the source map if Fengari is deployed as npm dependency. The artifact published to npm, has the source map detached. That is, the JS bundle doesn't reference it, even though it's included in the package. I don't know of build tool that can add references to those files.

Yes we can configure our build tool (webpack) to strip the source maps and references from our final bundle, but we can't tell it to re-attach the source map, for development mode.

A valid assumption would be, keep the source map referenced in our npm artifact, and let the client projects decide when to keep the source maps, and when to strip them.