closure-webpack-plugin

closure-webpack-plugin copied to clipboard

webpack v5 support

8

👋 I'm interested in using GCC with the latest version of Webpack (v5) but there seems to be an internal plugin issue. So far I've upgraded the demos to the...

jurassix

Error `Closure primitive methods (goog.provide, goog.require, goog.define, etc) must be called at file scope.`

1

Package version: 2.5.0 Node version: 14.15.0 OS: Ubuntu Minimal example: https://github.com/BeksOmega/closure-webpack-bug ### Reproduction steps 1) Clone the linked repro. 2) `npm install` 3) `npm run make-deps` 4) `npm run webpack`...

BeksOmega

Ensure error is logged when Closure fails

6

Fixes #162. Whenever the compiler process exits with non-zero code, we should be reporting some error back to Webpack. It looks like the on close for compilerProcess has some custom...

ian-craig

fix: webpack split chunks incompatibility using IIFE

4

Remove IIFE wrapper on standard build since it prevent multiple Webpack entries and/or chunks for working correctly. This is also one way to ask for confirmation on what is the...

Abdillah

children chunks are not able to access $jscomp polyfills because code is wrapped in IIFE wrapper

5

Migrating from https://github.com/roman01la/webpack-closure-compiler to this plugin. In standard mode output wrapper is hardcoded like this `outputWrapper: '(function(){%s}).call(this || window)',` Not sure how but this affects when there are dynamically loaded...

vishwanathd11

Reproducible Example at https://github.com/TeamPiped/Piped/tree/closure-compiler Some logs: ``` js/chunk-2d0f00ea.a822bc00.js from Terser "Export" statement may only appear at the top level error in js/chunk-fd847d92.225aa008.js /home/kavin/Workspace/Piped/node_modules/cache-loader/dist/cjs.js??ref--0-0!/home/kavin/Workspace/Piped/node_modules/vue-loader-v16/dist/index.js??ref--0-1!/home/kavin/Workspace/Piped/node_modules/eslint-loader/index.js??ref--13-0!/home/kavin/Workspace/Piped/src/components/WatchVideo.vue d84a17ffd546c1504bdc4368b25d8bbf RuntimeTemplate.moduleId(): Module /home/kavin/Workspace/Piped/node_modules/cache-loader/dist/cjs.js??ref--12-0!/home/kavin/Workspace/Piped/node_modules/thread-loader/dist/cjs.js!/home/kavin/Workspace/Piped/node_modules/babel-loader/lib/index.js!/home/kavin/Workspace/Piped/node_modules/@babel/runtime/helpers/esm/toConsumableArray.js has no id....

FireMasterK

Plugin forking threads for each chunk

2

We're seeing a threading and concurrency problem trying to upgrade our CC webpack plugin. We've moved from the old v3 version: https://www.npmjs.com/package/webpack-closure-compiler To the latest v4 plugin: https://www.npmjs.com/package/closure-webpack-plugin We're seeing...

djmetzle

I hit this when the plugin decided to use 'native' Closure but vcredist was missing on a build agent. The .exe was returning a non-zero exit code but no stderr...

ian-craig

Chunks are not processed

5

I have a minimal React setup [here](https://github.com/mfarhadpur/webpack-closure-compiler-example) that outputs three chunks (runtime, common, and main). The plugin seems to only process the main chunk and output blank for the others.

ghost

Unnecesary code

1

When we define de plugin with this configuration: ```js new ClosurePlugin ({mode : 'AGGRESSIVE_BUNDLE'}, {languageOut : 'ECMASCRIPT_2018'}) ``` this unnecesary code is included on top of compiled source: ```js (function(__wpcc){'use...

pabloalmunia