It would be nice to include a CHANGELOG.md in the repo, or list the various versions along with their changes in the Release tab, just to understand what a new version includes.

The devDependency webpack was updated from 4.19.0 to 4.19.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.9.2 of webpack was just published.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The adapter()-function is very noisy when it comes to outputting what it does. It might make sense to use something other then console.log in order to notify the user about what's going on. One approach would be to use the debug-package, which lets the user decide whether he wants to see the warning or keep it suppressed: https://www.npmjs.com/package/debug

function adapter() {
  // ...
    try {
        console.log('warning: couldn\'t find native brotli support in zlib library. trying to fall back to iltorb.');
        var iltorb = require('iltorb');
        return iltorb.compress;
    } catch (err) {
        console.log('warning: couldn\'t load iltorb library. trying to fall back to brotli.js.');
      // ...
    }
}

+ const debug = require('debug');
+ const warn = debug('brotli-webpack-plugin:warning');
+ const err = debug('brotli-webpack-plugin:error');

- console.log('warning: couldn\'t find native brotli support in zlib library. trying to fall back to iltorb.');
+ warn('couldn\'t find native brotli support in zlib library. trying to fall back to iltorb.');

Hi,

I used to have an Angular 11 project which was working well with brotli, right after the prod build it created the .br files in the dist folder as it supposed to.

However now that I have upgraded my application to Angular 14 brotli just stopped working and it only generates the pure javascript files which are like 9 times bigger than the old compressed one.

Do you have any guide or tips on how to make brotli compression work with Angular 14?

Tried with 2 different webpack configs, none worked:

var BrotliPlugin = require('brotli-webpack-plugin');
module.exports = {
	plugins: [
		new BrotliPlugin({
			asset: '[path].br[query]',
			test: /\.(js|css|html|svg)$/,
			threshold: 10240,
			minRatio: 0.8
		})
	]
}

const CompressionPlugin = require("compression-webpack-plugin");
const BrotliPlugin = require("brotli-webpack-plugin");

module.exports = {
  plugins: [
    new CompressionPlugin({
      algorithm: "gzip"
    }),
    new BrotliPlugin(),
  ],
};

Version 2.4.0 of iltorb was just published.

This version is covered by your current version range and after updating it in your project the build failed.

iltorb is a optionalDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

When I upgraded webpack to 3.5.5 and brotli-webpack-plugin to 0.4.0 , build gets stuck with no response, After digging further, i found that plugin bump was causing the issue. Reverting back to 0.3.0 works fine. My guess is that latest changelog is causing this break Moved compilation from this-compilation to emit stage.

I tried digging further,, but couldn't debug what's going wrong. I'm new to webpack and its plugin model internals.

Possibly related to webpack/webpack#3464 and webpack/webpack-dev-middleware#156

The devDependency webpack was updated from 4.35.3 to 4.36.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Just an FYI that this plugin gives the following warning in Webpack 4:

(node:16519) DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead

Not sure why I am getting this issue, I am not able to reproduce outside of my project

dyld: lazy symbol binding failed: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
  Referenced from: /Users/myname/workfolder/apps/node_modules/iltorb/build/bindings/iltorb.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
  Referenced from: /Users/myname/workfolder/apps/node_modules/iltorb/build/bindings/iltorb.node
  Expected in: flat namespace

webpack: "^4.20.2",
brotli-webpack-plugin: "^1.1.0",
node: v8.9.4
yarn: 1.15.2

if I downgrade the version of iltorb dependency, I am not getting this issue but If I use the default version of "iltorb": "^2.0.1" of brotli-webpack-plugin then I am getting this issue.

I am using yarn, any thoughts?

Add an option like in compression-webpack-plugin to remove compressed assets.

Node 11.7 landed Brotli support:
nodejs/node#24938
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V11.md#notable-changes

It'd probably be nice to publish a new major version of this plugin aimed at this node version and onwards.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.4 of iltorb was just published.

This version is covered by your current version range and after updating it in your project the build failed.

iltorb is a optionalDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.12.1 of webpack was just published.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.9.1 of webpack was just published.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi! This is more of a discussion post than a request. With Brotli support becoming fairly widespread (https://caniuse.com/#feat=brotli for those unfamiliar), it seems like it will become the defacto compression plugin over time. Has there been any consideration to merging the codebase with the existing webpack/compression-webpack-plugin ? I know you've already noted that the code is similar. It would be interesting as a way of promoting its usage to have it as a flag on the existing compression plugin (i.e. default to gzip for better support for old browsers, but provide a encodingType: "br" option, or similar.

Sorry if this is already in motion or been discussed; I couldn't find a similar issue, and brotli is a new discovery for me 😄

Hi,

in node version 12 we are getting error:

warning Error running install script for optional dependency: "/home/tratata/ha/node_modules/iltorb: Command failed.
Exit code: 1
Command: detect-libc prebuild-install || node-gyp rebuild
Arguments:
Directory: /home/tratata/ha/node_modules/iltorb
Output:
prebuild-install WARN install No prebuilt binaries found (target=12.16.3 runtime=node arch=x64 platform=linux)

If you use this plugin, the build fails: Segmentation fault: 11

angular 8.0.0
"@angular-builders/custom-webpack": "8.4.1",
"brotli-webpack-plugin": "^1.1.0",
"compression-webpack-plugin": "^6.0.3",

98% after emitting BundleBudgetPluginCannot read property 'size' of undefined
TypeError: Cannot read property 'size' of undefined
at.../node_modules/@angular-devkit/build-angular/src/angular-cli-files/utilities/bundle-calculator.js:48:58

custom-webpack.config.js :
const CompressionPlugin = require(compression-webpack-plugin); const BrotliPlugin = require(brotli-webpack-plugin); const path = require(path); module.exports = { plugins:[ new BrotliPlugin({ asset: '[fileWithoutExt].[ext].br', test: /\.(js|css|html|svg|txt|eot|otf|ttf|gif)$/, deleteOriginalAssets: true , }), new CompressionPlugin({ test: /\.(js|css|html|svg|txt|eot|otf|ttf|gif)$/, filename(info){ let opFile= info.path.split('.'), opFileType = opFile.pop(), opFileName = opFile.join('.'); return ${opFileName}.${opFileType}.gzip; } }) ], }

/usr/src/app/node_modules/brotli-webpack-plugin/index.js:16
        throw new Error('iltorb not found');
        ^

Error: iltorb not found
    at new CompressionPlugin (/usr/src/app/node_modules/brotli-webpack-plugin/index.js:16:15)
    at getPluginsConfig (/usr/src/app/webpack.config.js:268:5)
    at Object.<anonymous> (/usr/src/app/webpack.config.js:335:12)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
error Command failed with exit code 1.

Fails because iltorb is not a specific version [email protected]

compression-webpack-plugin has a feature, which lets filename prop to be a function which let you customize the file name. Can i make PR for that?

As usual, Windows users have issues native modules, and windows-build-tools are heavy and clumsy to use, especially in large dev teams.

Would it be possible to use devongovett/brotli.js instead?

Node 16 is now LTS, which means this repo no longer needs to be forward and backwards compatible between zlib and iltorb. In particular, this also solves another problem my org is facing which is that iltorb compilation is a cache miss under bazel because it leaves files with SHAs in them. Enforcing LTS versioning and dropping iltorb from the dep list would solve both of these problems. It would be considered a major, but it's a good move in general.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.1.0 of webpack was just published.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi there,

Currently, npm audit marks this package as high risk one, because one of this dependency has "Remote Memory Exposure" risk.

  High            Remote Memory Exposure

  Package         bl

  Dependency of   brotli-webpack-plugin [dev]

  Path            brotli-webpack-plugin > iltorb > prebuild-install > tar-fs >
                  tar-stream > bl

  More info       https://npmjs.com/advisories/1555

Hi, the release version that is being used to prebuild is not available in iltorb repository, could you take a look to update?

Thanks!

info looking for cached prebuild @ /Users/admin/.npm/_prebuilds/d5dc4d-iltorb-v2.4.0-node-v59-darwin-x64.tar.gz
http request GET https://github.com/MayhemYDG/iltorb/releases/download/v2.4.0/iltorb-v2.4.0-node-v59-darwin-x64.tar.gz
http 404 https://github.com/MayhemYDG/iltorb/releases/download/v2.4.0/iltorb-v2.4.0-node-v59-darwin-x64.tar.gz
WARN install No prebuilt binaries found (target=9.4.0 runtime=node arch=x64 platform=darwin)

Local Stack
node (9.4.0)
npm (5.6.0)
webpack (4.16.2)