-
## User Story
As a user I can delete a geometry in one of my layers of the map source via SQL command and force the maplibre GL JS map to refresh source, so that I can immediately see the deleted …
-
### Describe the bug
Using yarn PnP with workspaces causes swc to emit
```
ERROR failed to read input source map: failed to parse inline source map url
src.js.map
Caused by:
relati…
-
### What is the problem this feature will solve?
Hi,
I use Typescript, so I also use the `--enable-source-maps` flag for node, in order to debug easily the issues.
But actually, sometimes it is b…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the com…
-
### Describe the bug
When using [route groups](https://nextjs.org/docs/app/building-your-application/routing/colocation#route-groups) in NEXT.js, and submitting an error using `@bugsnag/js` `notify…
-
To get nicer stack traces we probably want to add support for parsing JS stacks that contain wasm frames to `package:source_map_stack_trace`.
-
We should implement a generic component that can take a list of coordinates and flux from an input file and generate a map already smoothed with the instrument beam.
This can for example be used for …
zonca updated
2 weeks ago
-
### What is the problem this feature will solve?
When debugging bundled/compiled/minified code, it's difficult to read a profile as locations and many function names point to the compiled code.
### …
-
When using micro-memoize version `4.0.10` in a react application, starting the application in development mode is giving the following warnings:
```
Failed to parse source map from '/home/user/Pro…
-
### Steps to reproduce
1. create a react project
2. configuring vscode debug:
![image](https://github.com/user-attachments/assets/22e02ade-0dac-4fcb-b774-7bb2cc83be75)
3. add break point
![imag…