Issue metadata
Sign in to add a comment
|
conflicts with babel browser plugin
Reported by
w...@optimal.com,
Jan 10 2017
|
||||||||||||||||||||||
Issue descriptionChrome Version : Version 55.0.2883.75 (64-bit) What steps will reproduce the problem? 1) Add a script element for the babel browser plugin: <script type='text/javascript' src="/lib/babel/browser.min.js"></script> 2) Add a script element for converting ES6 source: <script type="text/babel" src="/web/marketing/link.jsx" /> What is the expected result? The script loads and the ES6 transform is applied to the jsx source. What happens instead? The script no longer loads and a warning is issued. While a link preload and a script block with a dynamic insert is a workaround, I wanted to report the use case. Seems a little presumptuous that scripts cannot be of other types. Are we sure other browsers Please provide any additional information below. Attach a screenshot if possible. Original warning message: "Fetching scripts with an invalid type/language attributes is deprecated and will be removed in M56, around January 2017. See https://www.chromestatus.com/features/5760718284521472 for more details."
,
Jan 11 2017
,
Jan 16 2017
,
Jan 16 2017
>>we'll only start doing that in Chrome 56 That's correct, I was mistaken about the actual block in 55. If Babel in fact issues the XHR request, then I believe we can close this. I do not know of another language which needs loading in this way and hopefully ES6 support will be will be ubiquitous soon to avoid the need for non-native libs.
,
Jan 16 2017
Thank you for the followup. Closing the issue.
,
Jan 16 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by csharrison@chromium.org
, Jan 11 2017