v3.0.0-rc.2

[carhartl]

• Improve module setup in package.json to account for older Node.js versions - cc61b2c
• Reverted using browser field instead of main in package.json (for the UMD variant of the library): bundlers by default prefer it over module and will end up with a UMD module where ES may be preferred - cc61b2c

---

This discussion was created from the release v3.0.0-rc.2.

[proinc-bayles]

This release is broken when not loaded as a module. @carhartl

[emre42100]

        <script src="https://cdnjs.cloudflare.com/ajax/libs/js-cookie/2.2.0/js.cookie.min.js"></script>

[Miniland1333]

Issue has been opened at #698

[proinc-bayles]

        <script src="https://cdnjs.cloudflare.com/ajax/libs/js-cookie/2.2.0/js.cookie.min.js"></script>

Sure, but this likely broke the library in production for everyone who used the recommended script tag from the readme. It specifically says that it works without module support. There shouldn't be massive breaking changes from one rc to the next

[carhartl]

this likely broke the library in production for everyone who used the recommended script tag from the readme

As the readme also suggests strongly at the top is to use the latest stable version. If you decide to use a beta or release candidate in production it's your responsibility. There might be breaking changes, be it by accident or not. That is why there are beta and release candidates to begin with - to denote potential instability, or bugs.

I agree nevertheless that there shouldn't be such breaking changes for release candidates. It was a mistake and mistakes happen, it wasn't done on purpose.