mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
a52a2c28f1
After publishing coffeescript@2.3.1_1, I noticed that the version of
babel-runtime (1.2.5) that is bundled into the compile-coffeescript plugin
was complaining about the presence of @babel/runtime@7.0.0-rc.1 in the
node_modules directory of Meteor 1.7.1-rc.3 apps, thanks to code added
recently to work around breaking changes in @babel/runtime@7.0.0-beta.56:
4d5fff99eb
The easiest way to fix this problem in the short term is to give the
compile-coffeescript plugin its own reliable copy of the @babel/runtime
npm package, rather than delegating to the version installed in the app.
The ideal long-term way to fix this problem would be to stop precompiling
Meteor compiler plugins before publishing them, and instead treat them
like any other Meteor package, which are compiled after installation.
Another issue that could have been prevented if compiler plugins were
compiled upon installation, like other packages: #10148
cc @hwillson @abernix @GeoffreyBooth
coffeescript-compiler
Source code of released version | Source code of development version
This package supports the coffeescript package,
and any other packages that wish to compile CoffeeScript code into JavaScript.
Like the babel-compiler package, the actual
compilation is separated out from the build plugin so that packages besides
the official coffeescript package can compile CoffeeScript code.
Testing This Package
Testing the coffeescript package also tests this one:
./meteor test-packages packages/non-core/coffeescript