🚀 Compile v0/extensions in strict mode#29929
Conversation
|
Hey @rsimha! These files were changed: Hey @danielrozenberg! These files were changed: |
rsimha
left a comment
There was a problem hiding this comment.
One more successful experiment? Yay!
Also fixed a couple of bugs along the way / identified one more. They were all pre-existing bugs that this experiment just highlighted. Fixed:
Identified (lower pri, caused by pub error): |
|
This is currently failing the sourcemaps check, I believe I just need to update the check to look for this new first line (most likely 'use strict', TBD |
|
@rsimha: can you review my sourcemap-check fix? I couldn't easily figure out where the "generated" output for a file lives. I'm guessing the fix is correct, since the start column happened to move exactly the same number of chars as in |
rsimha
left a comment
There was a problem hiding this comment.
Thanks for fixing the sourcemap stuff, @samouri. I'll admit the test is not the easiest to maintain, but it's likely our best line of defense against real breakages. I've added some comments below. Let me know what you think.
|
Thanks for the review @rsimha. You made my job really easy :) |
* 🚀 Compile v0/extensions in strict mode * Update compile.js * sourcemap check: expect the usestrict * fix fix * raghu feedback * lint
Closes #19380
cc @lannka