Remove behaviour forcing types to be first in exports

[cefn]

Forcing "types" to be first in every export map breaks the fundamentals of custom conditions, in which package owners determine the priority order of conditions, including their own 'user conditions'.

Forcing "types" to be first in all exports is a regression we experienced breaking all builds in our monorepo via https://github.com/matzkoh/prettier-plugin-packagejson

• See https://nodejs.org/api/packages.html#resolving-user-conditions for the node feature of custom conditions
• See https://www.typescriptlang.org/tsconfig/#customConditions for the typescript integration of the feature
• See https://colinhacks.com/essays/live-types-typescript-monorepo for a worked example of how to use custom conditions to establish Typescript source resolutions within a monorepo

In that last article (written by the author of zod) is this very specific guidance, which is impossible when formatted by sort-package-json since 3.5.0

You should put your custom condition first. Order matters! It's important that your custom condition is the first one in the list (even before "types")

[keithamus]

It would be useful to have a test demonstrating the failure mode here. For example this simply removes the existing tests, but instead altering them to prove that types is not forced to the top will help us avoid future regressions.

[cefn]

Updated tests to include negative cases.

Fixes #393

[keithamus]

Generally this LGTM.

Let's have @fisker review this too, and merge.

[github-actions]

🎉 This PR is included in version 3.6.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀