babel-engine-plugin icon indicating copy to clipboard operation
babel-engine-plugin copied to clipboard

Webpack plugin that transpiles dependencies targeting Node.js versions newer than Node.js 0.10

Results 10 babel-engine-plugin issues
Sort by recently updated
recently updated
newest added

This PR addresses #11 and takes into account that author does not wish to entirely discard error messages (see discussion #13). Meaning that the warnings are ignored only when verbose...

Looking at the issues and open pull requests, I wonder if this project is still being maintained. @SamVerschueren how's it going?

I'm getting the following error while trying to use the library ``` node_modules\html-webpack-plugin\lib\compiler.js:194 return childCompilation.assets[helperFileName].source(); ^ TypeError: Cannot read property 'source' of undefined ```

This adds support for Babel 7 (fixes https://github.com/SamVerschueren/babel-engine-plugin/issues/16), by upgrading the two relevant packages (`babel-core`->`@babel/core` and `babel-preset-env`->`@babel/preset-env`). This was surprisingly easier than I expected! I ran into an issue running...

I'm still getting all the warnings, even with `verbose: false`. Did you perhaps mean to use an `||` operator instead of `&&` on [this line](https://github.com/SamVerschueren/babel-engine-plugin/blob/master/lib/babel-module-template.js#L20)? Happy to submit a PR...

A fix for #11 (all credits go to @timwis though, just implemented his find. Wanted my own branch with this fix to avoid a warning flood)

It seems `babel-engine-plugin` currently uses it's own `babel-core` version, which prevents proper use of the project's `.babelrc` file, in my case. `.babelrc` looks like this: ```json { "presets": [ ["@babel/preset-env",...

I am using your plugin in combination with [create-react-app-typescript](https://github.com/wmonk/create-react-app-typescript), in order to compile [mem](https://github.com/sindresorhus/mem) in production. When adding `babel-engine-plugin` I am left with a very vague webpack compiler error: >...

Currently the user has to add `babel-preset-env` every single time. Should we bake this in and provide good defaults? I think it's always good to have good defaults.