It‘s about https://github.com/sveltejs/rollup-plugin-svelte#pkgsvelte

I‘d rather not litter the package.json with non-standard fields, and it seems it isn‘t strictly necessary according to aforementioned documentation.

No, it's about the "package.json" not being accessible to the outside world. Doesn't matter who or what is trying to read the package.json file, anything outside of this module's own files can't look at the file cuz it's not defined as an export.

This is very standard & has been part of the ESM resolution algorithm and official documentation + example since very early days.

Thanks for the quick look @carhartl!

As @lukeed mentions above, this is not introducing the non-standard field (I assume you are referring the the "svelte" property). It is merely exposing the package's package.json file, which is often assumed to be accessible:

Warning: Introducing the "exports" field prevents consumers of a package from using any entry points that are not defined, including the package.json (e.g. require('your-package/package.json'). This will likely be a breaking change.
https://nodejs.org/api/packages.html#packages_package_entry_points

Thanks for the PR, and apologies for taking too quick a look..

Thanks, appreciate it!

@odeniso @lukeed I've created a new release so the fix becomes available: https://github.com/js-cookie/js-cookie/releases/tag/v3.0.1