You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am developing some front-end scripts in my projects, but it is hard to debug them, since webpack is not producing source maps. Apparently, __scripts.11ty.js processes and packages front end scripts, but source maps are not generated, I presume because of output file system being memory?
I tried setting devtool config property to inline-source-map, where webpack inlines source map as data-uri, but this does not work for me, at least in Firefox developer edition 95.
The text was updated successfully, but these errors were encountered:
Source maps started working with inline-source-map - it was some browser quirk perhaps. However, this method of source maps production is not recommended by webpack. I wonder, if default preferred eval method has advantages and if it has, how to enable this to actually produce maps.
I am developing some front-end scripts in my projects, but it is hard to debug them, since webpack is not producing source maps. Apparently,
__scripts.11ty.js
processes and packages front end scripts, but source maps are not generated, I presume because of output file system being memory?I tried setting devtool config property to
inline-source-map
, where webpack inlines source map as data-uri, but this does not work for me, at least in Firefox developer edition 95.The text was updated successfully, but these errors were encountered: