Jest sets the env variable to test, so I had to add my presets to the env setting in .babelrc: { “plugins”: [“syntax-dynamic-import”, “transform-runtime”], “presets”: [ [ “es2015”, { “modules”: false } ], “react”, “stage-0” ], “env”: { “start”: { “presets”: [ “react-hmre” ] }, “test”: { “presets”: [“es2015”, “react”, “stage-0”] } } }
You’re using a combination of Babel 6 and Babel 7. There is no guarantee of compatibility across versions: “@babel/core”: “^7.0.0-beta.40”, “babel-cli”: “^6.26.0”, “babel-loader”: “^8.0.0-beta.0”, “babel-plugin-lodash”: “^3.3.2”, “babel-plugin-react-transform”: “^3.0.0”, “babel-preset-react”: “^6.24.1”, should be “@babel/core”: “^7.0.0-beta.40”, “@babel/cli”: “^7.0.0-beta.40”, “babel-loader”: “^8.0.0-beta.0”, “babel-plugin-lodash”: “^3.3.2”, “babel-plugin-react-transform”: “^3.0.0”, “@babel/preset-react”: “^7.0.0-beta.40”, and query: { presets: [‘react’, ‘es2015’], plugins: [‘transform-class-properties’] } would be … Read more
Delete the package-lock.json file and the node_modules directory in your project and then run npm install on your terminal.
Apparently, ES6 doesn’t need namespacing because each file is a separate module. Not exactly. Each module does have its own scope, that is correct, but not every file is a module. There still are scripts in ES6 that work just like those from ES5, and are executed in the global scope. In those scripts, you … Read more
Since you have @Decorators enabled in Babel …I’ll fine-tune this answer to work with your specific setup. 1. You’re missing HTTP_PROVIDERS The HTTP_PROVIDERS constant includes a number of functions required to handle HTTP requests/responses. import {Http, HTTP_PROVIDERS} from ‘angular2/http’; @Component({ selector: ‘login’, providers: [ HTTP_PROVIDERS ] }) 2. You need to desugar the DI (Dependency … Read more
Testing in ES6 with Mocha and Babel 7. Look here: https://dev.to/bnorbertjs/my-nodejs-setup-mocha–chai-babel7-es6-43ei or http://jamesknelson.com/testing-in-es6-with-mocha-and-babel-6/ npm install –save @babel/runtime npm install –save-dev @babel/plugin-transform-runtime And, in .babelrc, add: { “presets”: [“@babel/preset-env”], “plugins”: [ [“@babel/transform-runtime”] ] }
It’s the same as defining the function as a variable but just adding export to the front e.g. (using ES6 syntax) export const render = () => ( // Some other JSX ); or alternatively export var render = function() { return ( // Some other JSX ); };
See the babel docs: NOTE: By default all requires to node_modules will be ignored. You can override this by passing an ignore regex. Generally the expectation is that modules in node_modules will already have been transpiled ahead of time, so they are not processed by Babel. If you will not be doing that, then you … Read more
By default, Babel 6.x requires you to enable an explicit set of transformations. The standard es2015 preset converts ES6 to ES5, however IE8 is not ES5-compatible. In this case, if you look at the plugins list, you will see transform-es3-member-expression-literals transform-es3-property-literals These will convert your properties to be compatible with IE8. Generally in Babel 6.x … Read more
Babel 7 does not need ts-loader. As of Babel 7 the ts-loader is unnecessary, because Babel 7 understands TypeScript. Complete details of a TypeScript + Babel7 + Webpack setup are here. An overview of the set up without ts-loader. Install Babel’s TypeScript support. Only @babel/preset-typescript is mandatory; the other three add additional features that TypeScript … Read more