Open axetroy opened 7 years ago
@axetroy Not sure if this issue is related to the plugin, please make sure your Webpack config is valid. If everything is ok on your side, a minimal repro example would be nice to have so I can reproduce the issue.
@roman01la I am pretty sure the Webpack config is valid.
only load this plugin and Babel. Babel work as expect. once load plugin, it throw this error.
it this plugin not compatible with Webpack2?
@axetroy It is compatible. I need a minimal project to reproduce the issue, so I can help you.
@roman01la thanks, I'm organizing the project response you soon
@roman01la
I create a mini project in here https://github.com/axetroy/webpack-closure-compiler-example
run the command
git clone https://github.com/axetroy/webpack-closure-compiler-example.git
yarn # npm install
yarn run build # npm run build
@axetroy thanks, I'll try this later today and get back to you
I'm receiving the same exact issue on Windows. I have an npm script with a MINIFY
flag that is set to true
in production and adds this plugin to the webpack. The development build works fine and setting the MINIFY
flag to false
in production also works.
@axetroy I was about to test the project but the repo appears to be deleted. Could you please bring it back? Sorry for delay.
@roman01la recommend looking up this webpack loader-utils issue and setting process.traceDeprecation = true
in (one of) your webpack config files. The line goes somewhere in the header, outside the webpack config object. If it is really your plugin then it will report accordingly.
This is actually not an issue with this plugin. ADVANCED compilation with Google Closure Compiler requires you to use externs when referencing external JavaScript. E.g window
or any third party node_modules, such as the one listed in above output (https://github.com/axetroy/event-emitter.js) that you are including. I recommend taking a look at the docs for ADVANCED compilation located here: https://developers.google.com/closure/compiler/docs/api-tutorial3
Does anyone still experience the issue?
I config the plugin use example in webpack@2.2.1
build and throw an error