Tooling integrations for package.json#exports

[bmeck]

I've seen various issues with understanding the package.json#exports,imports fields.

1. Lack of linting (E.G. package.json diagnostics in --module nodenext microsoft/TypeScript#46861 )
2. Lack of convention. No official recommendations of ordering of conditions in typical application/framework. (E.G. https://twitter.com/AndaristRake/status/1498701683093823494 )
3. Lack of discoverability. Understanding which path in your own package will be taken / altering the resolution of such.
4. Lack of specification granularity / need to be reimplemented in userland (E.G. https://twitter.com/sebmarkbage/status/1498691681750765577 )

It would be good to have some way for tooling to provide these and/or make recommendations for tools that do scaffolding and the general user of Node.js to reference.

[ljharb]

fwiw, I'm continuing to refine https://v-npmjs-com.adclosenn.dev/ls-exports (it's still not caught up to the latest node features), and once it's up to par, I'll be updating resolve to support both fields, using the test fixtures from list-exports for verification.