docs: add missing type field description for package.json

[kenshanta]

Add formatted description with links & examples for the package.json type field.

References

• Related to PR 1359 Issue 1338
• Fixes issue 1204 PR 1359

[kenshanta]

Props to @reggi for pointing out where the changes should be introduced.
Appreciated! 🎩

[reggi]

Hey sorry for the other PR, I was trying to get a handle on other missing fields too. I do think that fields governed and documented by other bodies, whether it be typescript or node.js should just more or less be minimal in description and link directly to the documentation. We've recently added type: commonjs as the default property on npm init. So I think it's worth noting that this is parity with how the field works now.

I think the gist of what i'm getting at is when / if node updates this field we wouldn't be out of date with their docs.

---

type

See Node.js documentation on type here.

Property that governs if Node.js will interpret package as CommonJS (cjs) or ECMAScript Module (esm). When this field is undefined it is interpreted as the value commonjs.

[kenshanta]

Since the changes are for the documentation: long and detailed descriptions with examples (like in most other attributes) are very much preferred especially when taking beginners into consideration rather than short and almost "code-like" descriptions.

But hey that's just my opinion