-
Notifications
You must be signed in to change notification settings - Fork 83
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
Add Sourcemap header #2184
Add Sourcemap header #2184
Conversation
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
features/sourcemaps.yml
Outdated
@@ -0,0 +1,5 @@ | |||
name: Source maps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should make this name more specific to the fact that this feature is about the HTTP header. There are multiple ways to load source maps into DevTools, and using the HTTP response header is one of them.
Other ways include:
- By including comments in JS:
//# sourceMappingURL=...
- Automatically, by using Edge DevTools' Symbol Server integration.
- Manually in DevTools.
Maybe change the name to "Source map header"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Patrick, in this case, yes, I think the correct thing would be to make this feature just about the header.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy to see this merge, but I'll leave it to Patrick or Florian to decide whether to merge with or without Patrick's re-review. 😄
Here I'm not sure if we want "SourceMap" or "Source maps". I think more people talk about it as "Source maps"
Edit: As Patrick notes, this is just the header and not general source maps support