Create markdown table skeleton for initial package.json fields

[rxmarbles]

Opening this issue in reference to openjs-foundation/package-metadata-interoperability-collab-space#21. We will continue to utilize this repo to house this data.

[reggi]

👋 npm here I'm down to help, I have a couple of sources of truth

[wesleytodd]

Hey @reggi! I would love to partner up on this. I have been trying to catch up on my notifications but have a todo I volunteered to start which was opening a PR for a bare scaffold for each package.json field, which would enable folks to start filling in small details without the block of having to figure out the formatting and stuff on their own. Is that something you would be up for helping with? If you wanted to discuss a plan for this I am available in the OpenJS slack.

[reggi]

Some resources:

• I've been trying to keep this type definition up to date: https://github.com/npm/types/blob/main/types/index.d.ts#L104-L144
• sort-package-json has a lot of properties in there that aren't used by npm: https://github.com/keithamus/sort-package-json/blob/main/defaultRules.md
• There's this list here that I made recently (this has some deprecated fields, but there are others deprecated fields as well): https://github.com/npm/package-json/blob/main/lib/sort.js#L11-L50
• There's the schema store json schema definition that things like vs code use (which isn't perfect either) : https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/package.json
• Package.json docs isn't perfect, and deprecated fields only show on pages older versions 😢 https://docs.npmjs.com/cli/v11/configuring-npm/package-json

If this is specifically related to "npm init" it's every field exported from this file here: https://github.com/npm/init-package-json/blob/main/lib/default-input.js