Add missing "type": "module" to package.json for Vite resolution

[jorenbroekema]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

latest

Link to runnable example

No response

Steps to reproduce

• import { toHtml } from 'hast-util-to-html' in a JS file
• Run with Vite (e.g. dev server)

Expected behavior

Some developer tools assume any module is a CommonJS module unless "type":"module" is specified in package.json.
I don't particularly agree with that approach and I'm not sure why the Vite maintainers decided to be more "dumb" about it in their resolution logic versus what they had before, but it seems to me that providing this meta information doesn't hurt and helps tools understand more clearly what format a module is.

Expected: "type": "module" in package.json

Actual behavior

Missing "type": "module" in package.json, results in tools thinking the module is CommonJS format.

Affected runtime and version

[email protected]

Affected package manager and version

[email protected]

Affected OS and version

No response

Build and bundle tools

Vite

[wooorm]

hast-util-to-html/package.json

Line 28 in fa18749

"type": "module",

Update your dependencies and built tools

[jorenbroekema]

Ah sorry, I read over it completely. 👍

[wooorm]

no problem!