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
Really liking playing around with Framework, congrats on an awesome release!
We might like sourcemaps to go out of fashion(?) but I generate ESM and keep a sourcemap.
I'm importing that ESM using a regular import:
import * as model from './cul/calcs_esm/cul_scope_0.js'
The file ends with //# sourceMappingURL=cul_scope_0.js.map: a reference to the sourcemap file, but because this file isn't deployed (to dist or to observablehq.cloud) or served (with npm run dev), then it isn't available to devtools - see error:
Should/can Framework detect and serve sourcemaps?
On Quarto I include sourcemap files as a resource and they gets served - this could be a workaround, but might need to be a more particular one given Frameworks directory structure (_file, _import etc.)
Thanks!
Declan
The text was updated successfully, but these errors were encountered:
Hi,
Really liking playing around with Framework, congrats on an awesome release!
We might like sourcemaps to go out of fashion(?) but I generate ESM and keep a sourcemap.
I'm importing that ESM using a regular import:
import * as model from './cul/calcs_esm/cul_scope_0.js'
The file ends with
//# sourceMappingURL=cul_scope_0.js.map
: a reference to the sourcemap file, but because this file isn't deployed (todist
or toobservablehq.cloud
) or served (withnpm run dev
), then it isn't available to devtools - see error:Should/can Framework detect and serve sourcemaps?
On Quarto I include sourcemap files as a resource and they gets served - this could be a workaround, but might need to be a more particular one given Frameworks directory structure (
_file
,_import
etc.)Thanks!
Declan
The text was updated successfully, but these errors were encountered: