-
-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove jsesc #490
Remove jsesc #490
Conversation
boopathi
commented
Apr 3, 2017
•
edited
Loading
edited
- Fix unnecessary escaping in string concatinaion #440, fix Invalid string concatenation breaks Lodash _.template method #413
- Related Escape "</script" when inlining strings #384, Allow for exceptions in string concat inlining #382
Codecov Report
@@ Coverage Diff @@
## master #490 +/- ##
=========================================
- Coverage 82.62% 82.6% -0.02%
=========================================
Files 35 35
Lines 2630 2627 -3
Branches 928 927 -1
=========================================
- Hits 2173 2170 -3
Misses 279 279
Partials 178 178
Continue to review full report at Codecov.
|
Hmm, the problem in #413/#440 isn't A solution entirely in the constant folding plugin would be to manually replace |
Yes. The problem is running jsesc twice. Babel generator already passes all String Literals via jsesc. I'll add a PR to babel to pass isScriptContext to the generator- but probably will be added to the current track - 7.0. And remove jsesc from babili and this option after that. |
Yes but this would still run jsesc twice, wouldn't it? |
Will remove jsesc after babel/babel#5581 . |
ed5f866
to
9b67cfc
Compare
9b67cfc
to
58d3571
Compare
For context, see #440 (comment). This patch is a part of that solution. 👍 |
Yes !! babel/babel#5581 .. That's why I kept #382 open. So we can have an enhancement issue open rather than a bug open - and merged this PR. |