Version 2.1

[svenzik]

WE2-1179

• build: include source maps, add exports, update versions
• build: version bump to 2.1.0-beta.1

[taneltm]

The module property should be removed.

https://stackoverflow.com/questions/42708484/what-is-the-module-package-json-field-for

The module field is not officially defined by Node.js and support is not planned. Instead, the Node.js community settled on package exports which they believe is more versatile.

For practical reasons JavaScript bundlers will continue to support the module field. The esbuild docs explain when to use module as well as related fields main and browser.

---

This field came from a proposal for how to integrate ECMAScript modules into node. Because of this, it's reasonable to expect that the file path in this field is an ECMAScript-style module. This proposal wasn't adopted by node (node uses "type": "module" instead) but it was adopted by major bundlers because ECMAScript-style modules lead to better tree shaking, or dead code removal.

For package authors: Some packages incorrectly use the module field for browser-specific code, leaving node-specific code for the main field. This is probably because node ignores the module field and people typically only use bundlers for browser-specific code. However, bundling node-specific code is valuable too (e.g. it decreases download and boot time) and packages that put browser-specific code in module prevent bundlers from being able to do tree shaking effectively. If you are trying to publish browser-specific code in a package, use the browser field instead.

[taneltm]

The main property should be removed. It wasn't there in version 2.0.

This should be double checked. In which Node version was exports property added and which Node version is supported.

https://nodejs.org/api/packages.html#nodejs-packagejson-field-definitions

"main" - The default module when loading the package, if exports is not specified, and in versions of Node.js prior to the introduction of exports.

[taneltm]

Consider the following:

export {
  ActionOptions,
  LibraryAuthenticateResponse as AuthenticateResponse,
  LibraryGetSigningCertificateResponse as GetSigningCertificateResponse,
  LibrarySignResponse as SignResponse,
  LibraryStatusResponse as StatusResponse,
};

[taneltm]

1. In tsconfig.json we should change moduleResolution from node to node10.

   node: Deprecated, use "node10" in TypeScript 5.0+ instead

2. README.md should be updated to reflect changes done in simplifying importing Web-eID library types.