TypeError: Invalid non-string/buffer chunk in v0.3 (worked in v0.2).

[webpack-contrib]

TypeError: Invalid non-string/buffer chunk in v0.3 (worked in v0.2).

[mathieumg]

Fixed in v0.3.1, this could be closed!

[graingert]

@jornare v0.3.0...v0.3.1

[jsg2021]

@Icehunter "^0.x.y" is special case... just as @cchamberlain said. when the major is "0" the caret makes minor locked.

[samkelleher]

Can confirm that rolling back to 0.2 works normally with no other changes.

[calvinl]

Just saw this error as well. Confirmed rolling back to 0.2.0 works.

[mjrussell]

👍

[AymanNatsheh]

rolling back to 0.2.0 works

[yacodes]

Also facing this issue.

[hqxluoyang]

And I just happened to meet.

[Icehunter]

I have this same issue as well. My bigger concern is why this repo is not following semver? I saw 0.3.0 was published as a "breaking change". Should that not have been 1.0.0? Because NPM uses ^X.X.X by default this just possibly will break anyone's usage unless they explicitly hardcode versions.

[Icehunter]

Fix proposed:
#18

[jsg2021]

@Icehunter it is kindof semvar :)

http://semver.npmjs.com/ put in "^0.2.0" for "compression-webpack-plugin" and see that only 0.2.0 is highlighted.

[Icehunter]

@jsg2021 They may not have updated the front portion of the site but the default behavior of NPM has changed since 4+ (to the best of my knowledge).

Such as if you do:
npm i hapi@^11.0.0
[email protected] /Users/icehunter/GitHub/nodeplayground
└── [email protected] extraneous

The same if I did:
npm i hapi@^10.0.0
[email protected] /Users/icehunter/GitHub/nodeplayground
└── [email protected] extraneous

If you click through to https://docs.npmjs.com/getting-started/semantic-versioning you can see that they have it as:

Patch releases: 1.0 or 1.0.x or ~1.0.4
Minor releases: 1 or 1.x or ^1.0.4
Major releases: * or x

So ^1.0.4 and 1.x are the same.

[cchamberlain]

This has been breaking my builds and throwing lots of errors since the inclusion of the node-zopfli stuff on windows.

[cchamberlain]

Also @Icehunter, anything semver 0.x.x is considered initial development and may change at any time. See http://semver.org/#spec-item-4

[Icehunter]

Fair enough. I'll wait till this hits 1.0 to use it then. Personally though even if it's under 0.X I follow it as much as I can :)

[cchamberlain]

@Icehunter I've been using 0.2.0 in prod for some time on Windows and OSX and haven't had any issues until 0.3.0. 🍻

[graingert]

yeah I get this problem also

[robbyoconnor]

I got this issue too

[zjhiphop]

Any progress for this issue?

[zjhiphop]

The 0.2.0 works, but the build result seems strange.
The config i used:

{
        asset: "[path].gz[query]",
        algorithm: "gzip",
        test: /\.js$|\.html$/,
        threshold: 10240,
        minRatio: 0.8
    }

After build, there generated a file named with '[path].gz[query]', that's so boring. Any one could help with it?

[calvinl]

@zjhiphop that's the syntax for 0.3.0. Try it with {file}.gz instead if you're using 0.2.0.

[dshorowitz]

+1 Also have this issue

[jornare]

All the change I can see in 1.3.1 is the bump in version. Am I mistaken?