-
# You should generate sourcemap.json so we can easily get IntelliSense autocomplete and no errors from Luau LSP because of invalid instances to make contribution more efficient.
-
### 🚀 Feature Proposal
At the moment, in https://github.com/thymikee/jest-preset-angular/blob/main/src/ng-jest-transformer.ts, esbuild won't be able to process any typescript file since the loader is…
-
### Summary
When I run the project after `npm install` there was the bellow error:
`'GENERATE_SOURCEMAP' is not recognized as an internal or external command,`
### Page
package.json
#…
-
It's possible the bug described in the title only happens if Plugins are used to modify the output. In my particular case I discovered this issue because I'm transpiling SASS which esbuild doesn't han…
-
Sourcemaps are currently not supported meaning that stack traces will be from transpiled JS sources. This is not ideal for debugging purposes.
The parcel bundler has implemented support for source ma…
m-rph updated
5 months ago
-
I did a quick (incomplete) test with esbuild, and could get much better sourcemaps than webpack already.
Might make sense to use rollup due to better plugin support, but haven't tested sourcemap qu…
-
It would be nice if this plugin supported writing sourcemaps to disk.
It could support inline sourcemaps, linked/external sourcemaps, or both. Inline would be easier to add, but linked ones sound m…
-
### Summary
As a consumer of Calcite Components used through another project, it is sometimes helpful to set breakpoints in Calcite Components source. Examples of when this is helpful include debuggi…
-
**Describe what happened**
I'm trying to configure DataDog for error monitoring for my Expo app per this [guide](https://docs.datadoghq.com/real_user_monitoring/error_tracking/expo/). I have the `i…
-
### Describe the problem
When using error reporting tools like Sentry/Bugsnag/Rollbar, etc. the stack trace is much more readable if you upload your sourcemaps.
Currently, when setting `build.sour…