0.1.16 breaks Webpack 4 about swc-loader HOT 10 CLOSED

from swc-loader.

Hello ,

I had same problem and solve problem

And solved the problem

It's fixed version swc-loader in package.json

"swc-loader": "^0.1.15" => "swc-loader": "0.1.15"

I'm in same enviroment webpack 4

from swc-loader.

@minsoku Yep thanks, that's how I fixed it as well!

However I'm wondering if Webpack 4 users will forever be stuck on 0.1.15, because of this change in implementation details.

from swc-loader.

I set latest to 0.1.15 and published 0.2.0 instead

from swc-loader.

I set latest to 0.1.15 and published 0.2.0 instead

감사합니다 ~~

from swc-loader.

I set latest to 0.1.15 and published 0.2.0 instead

Sorry but how does this solve the problem? 0.1.x --> 0.2.x is a minor bump, which shouldn't contain breaking changes.

from swc-loader.

@yazeedbz No It's not a minor bump

from swc-loader.

Read semver docs

from swc-loader.

@kdy1 From the semver docs, it seems changes that break users' apps is a major change (1.x.x --> 2.x.x)

• Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
• Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API.

from swc-loader.

@kdy1 Oh man you're right...I'm sorry about that 😓

• Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Thanks for patiently clarifying!

from swc-loader.