-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Disable sourcemaps support in babel if input is big #2345
Conversation
This prevents babel from using up a lot of memory (3.5x as much as before source maps) on really big inputs.
Co-authored-by: na-- <[email protected]>
js/compiler/compiler.go
Outdated
c.logger.Warnf("the source for `%s` needs to go through babel but is over %d bytes. "+ | ||
"For performance reasons sourcemaps support will be disabled for this particular file.", |
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.
Should we mention K6_DEBUG_SOURCEMAP_FILESIZE_LIMIT
?
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 shouldn't mention this, for a couple of reasons:
K6_DEBUG_SOURCEMAP_FILESIZE_LIMIT=whatever k6 cloud
won't work- we intend to get rid of this option eventually
So we shouldn't really document this. It's a temporary option until we get rid of Babel. We can always mention it and the caveats if someone asks in the forum.
code, srcMap, err = c.babel.transformImpl(c.logger, src, filename, c.Options.SourceMapLoader != nil, inputSrcMap) | ||
sourceMapEnabled := c.Options.SourceMapLoader != nil | ||
maxSrcLenForBabelSourceMapOnce.Do(func() { | ||
// TODO: drop this code and everything it's connected to when babel is dropped |
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.
Do we have an issue to link?
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.
#2296 (comment) maybe? 🤔
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.
mmm...if we don't have one yet, I'm for creating one dedicated with the steps we plan for dropping babel. For example, it would be useful to have somewhere a link to dop251/goja#348 and this potential new issue could be a good candidate, IMHO.
It's mentioned in your comment, sorry, my fault.
Co-authored-by: Ivan <[email protected]>
Co-authored-by: Ivan <[email protected]>
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.
LGTM 👍
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.
LGTM 🤞
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.
LGTM
This prevents babel from using up a lot of memory (3.5x as much as before source maps) on really big inputs. Co-authored-by: na-- <[email protected]> Co-authored-by: Ivan <[email protected]>
This prevents babel from using up a lot of memory (3.5x as much as
before source maps) on really big inputs.