I suggest users migrate to the native ecmascript package. Here is how one user accomplished this recently:
Important information if you have recently updated to v1.0.3 or higher, which introduced configuration through
.babelrc. Please rename.babelrctobabel.json, because under certain circumstances Babel reports errors when it encounters a custom keys inbabel.rc, such as "verbose". Thus, I have reverted to usingbabel.jsonfrom v1.0.5 onwards. Apologies for any inconvenience.
This package is meant to be used with Angular-Meteor and the corresponding angular package.
If you are not working with angular-meteor then consider using Meteor's own ecmascript package. However, if you do need the extra bits of goodness that this package provides over and above what ecmascript does, then it's ok to use this package also. Even if you're not using AngularJS, it will not harm your code.
meteor add pbastowski:angular-babelThe discussion here is for Meteor 1.2 only.
Here is the list of Babel transformers in this package that are not in the ecmascript package:
- es5.properties.mutators
- es6.modules
- es6.regex.sticky
- es6.regex.unicode
- es6.tailCall
- es6.templateLiterals
- es7.decorators (stage 1)
- es7.classProperties (stage 0)
- es7.exportExtensions (stage 1)
- es7.comprehensions (stage 0)
- es7.asyncFunctions (stage 2)
- es7.doExpressions (stage 0)
- es7.exponentiationOperator (stage 3)
Please note that all es7 transformers are considered experimental, especially those at Stage 0 and 1.
Place babel.json at the root of your project to override certain default settings. This file is completely optional and may contain the following in JSON format. The values below are the default configuration.
{
"verbose": false, // true shows files being compiled
"debug": false, // true displays this config file
"modules": "common", // what module format Babel should use. See
// Babel documentation for "modules" option.
"blacklist": ['useStrict'], // Do not change this unless you know
// very well what you are doing.
"stage": 0, // see Babel documentation for stage option.
"extensions": ["js"] // "js" means compile all ".js" files.
}
Babel does not include a module loader, so statements such as below, will not work out of the box
import {x, y, z} from "modulename";However, if your modules setting is { "modules": "system" } then we can use pbastowski:systemjs to load modules compiled with Babel. For CommonJS modules, which is the default "modules" setting, we can use pbastowski:require.
Meteor 1.2 or higher
So, you have configured Babel through babel.json to output SystemJS modules, like this:
{ "modules": "system" }
Well done! Now you need to know how to use these modules in your code.
SystemJS modules are assigned a name based on their file name within your project. Below are some examples that show how a file name is converted to a module name, which you can import:
| file name | module name |
|---|---|
| client/app/app.js | client/app/app |
| client/feature1/feature1.js | client/feature1/feature1 |
| client/feature1/lib/xxx.js | client/feature1/lib/xxx |
| client/lib/angular-messages.min.js | client/lib/angular-messages.min |
meteor add pbastowski:systemjs
Next, in the body section of your index.html file you need to import the JS file that kicks off your application. For our example that file is client/index.js.
<head>
<title>My App</title>
</head>
<body>
<app>Loading...</app>
<script>
System.import('client/index');
</script>
</body>Below is a sample client/index.js file. Remember that the innermost imports, those inside app and feature1, will be executed first. Then, the rest of the code in index.js will be executed in the order it is listed in the file.
In the example below, first client/app/app will be imported and executed followed by client/feature1/feature1.
import 'client/app/app';
import 'client/feature1/feature1';Meteor 1.1 or higher
When the module format is common, which is the default for this Babel plugin, you don't actually have to do anything special as long as you don't import or export in your ES6 files. Babel will compile your code and output files that will be loaded and executed just like any normal non-compiled JS files would be.
If you use import ... from or export syntax in your ES6 code you may see errors in your dev console complaining about a missing require. To get around that, I have created the package pbastowski:require, which implements just enough of require and module.exports to enable you to export and import in Meteor apps.
Try it and see if it works for you:
meteor add pbastowski:require
See the Babel website
If Meteor refuses to update your package to the latest Meteor 1.2 version, you may have to convince it to do so like shown below. Change the version number to whatever version that you actually want.
meteor add pbastowski:[email protected]The latest version of pbastowski:angular-babel for Meteor 1.1 is 0.1.10