chore: set type to module in package.json

[vursen]

Description

The type property of a package.json is commonly used by frontend tooling for detecting whether the package's entry point is a CJS or ES module. If no property is specified, the entry point may be treated as a CJS module according to Node.js docs which is not true in the case of Vaadin web components. To illustrate the situation, here is a warning that Vite shows when you import a Vaadin web component:

@vaadin/vaadin-time-picker doesn't appear to be written in CJS, but also doesn't appear to be a valid ES module (i.e. it doesn't have "type": "module" or an .mjs extension for the entry point). Please contact the package author to fix.

This PR explicitly sets the type property to module to avoid possible misinterpretation.

Related to vaadin/flow#12574

Type of change

• Internal

[web-padawan]

LGTM. Rebased the PR, also formatted package.json files using Prettier:

npx prettier packages/**/package.json --write

BTW, this isn't currently covered by precommit hook, I'll fix that separately.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication