Fix CoffeeScript transpilation #358
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GeoffreyBooth
force-pushed
the
fix-coffeescript-transpilation
branch
from
67feaab to
e9adff3
Compare
This reverts commit e9adff3.
Collaborator
|
Thanks! 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since CoffeeScript 2 came out, CoffeeScript outputs ESNext code that may run fine in modern Node and Chrome but requires Babel transpilation to run in older runtimes like IE11. This PR updates
vue-coffeeto tag its CoffeeScript 2-generated output as requiring Babel transpilation, so that.vuefiles with CoffeeScript code work in older browsers like IE11.