Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] source map generation #61

Closed
vstefanovic97 opened this issue Jan 19, 2024 · 1 comment · Fixed by #62
Closed

[Feature request] source map generation #61

vstefanovic97 opened this issue Jan 19, 2024 · 1 comment · Fixed by #62

Comments

@vstefanovic97
Copy link

I would like to request for content-tag to also return source maps for the files it parses, so that we can map the parsed .js/.ts file back to the original .gjs/.gts file.

Example where this can be useful, when we are building a v2 addon with the standard v2 blueprint with rollup and let's say we want to use babel-plugin-istanbul to instrument our code, we would need the original source maps so that istanbul would know exactly how to map it's coverage to the original .gjs/.gts source files.

@ef4
Copy link
Collaborator

ef4 commented Jan 19, 2024

The rust side of this library already supports source maps, we just need to add an option to the JS bindings to expose that usefully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants