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
While diagnosing and fixing js-temporal/temporal-polyfill#192, I found that JSBI has the same bug: the package's sourcemap points to files that don't exist in the package. This causes debug console errors in some environments like the VSCode debugger.
For example, here's what I see in the debug console when I run my JSBI-using app in the VSCode debugger:
Could not read source map for file:///Users/[redacted for privacy]/node_modules/jsbi/tsc-out/jsbi.mjs: ENOENT: no such file or directory, open '/Users/[redacted for privacy]/node_modules/jsbi/tsc-out/jsbi.js.map'
The fix that I proposed in js-temporal/temporal-polyfill#193 is to add the tsc-out folder to the package. The lib folder should also be added. I suspect that the same fix may work here too. There may be other fixes possible too.
The text was updated successfully, but these errors were encountered:
I'm less confident that I understand the bundler config in this repo than in https://github.com/js-temporal/temporal-polyfill. In particular, I'm not sure how the browser-facing bundles work here, and I was worried that increasing the size of the browser bundle might be bad. So I was thinking that it might be better for someone who knows this repo better (like @12wrigja?) to PR a fix here?
While diagnosing and fixing js-temporal/temporal-polyfill#192, I found that JSBI has the same bug: the package's sourcemap points to files that don't exist in the package. This causes debug console errors in some environments like the VSCode debugger.
For example, here's what I see in the debug console when I run my JSBI-using app in the VSCode debugger:
The fix that I proposed in js-temporal/temporal-polyfill#193 is to add the
tsc-out
folder to the package. Thelib
folder should also be added. I suspect that the same fix may work here too. There may be other fixes possible too.The text was updated successfully, but these errors were encountered: