`threshold null gzip` error
See original GitHub issueI’ve noticed that the docs use maxSize
in the config, since the tagged release hasn’t happened yet to change the internals to use maxSize
it uses threshold
instead. Giving an error like this
./dist/assets/es5.min.js: 65.19kB > threshold null gzip
To fix change the property in your package.json
to from maxSize
to threshold
.
Just popping this here for anyone getting the error.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Threshold of `false` seems confusing · Issue #144 - GitHub
Is threshold option being false means never compress no matter response size, or default threshold of 1 KiB, or something else?
Read more >unable to Compress into gzip in webpack - Stack Overflow
I want to compress my react app into gzip,actually it is 2.2 mb so I used compression-webpack-plugin but i'm unable to compress
Read more >Unexpected end of file. Gzip compressed file - Super User
A workaround for uncompressing a file when gzip fails with "unexpected end of file" is to use zcat (also usually provided by the...
Read more >Gzip compression with Node.js - Medium
Compression in Node.js and Express.js decreases the amount of ... Gzip (gzip): The most widely used compression format for server and ... threshold:...
Read more >GZIPOutInterceptor (Apache CXF JavaDoc 3.2.0 API)
To handle gzip-encoded input messages, see GZIPInInterceptor . This interceptor supports a compression threshold (default 1kB) - messages smaller than this ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@reznord, this is my bad.
I haven’t published your change to npm
Yeah, there are some that I haven’t tested yet. Soon, I promise!