🐛 Bug: `sort-collections` should not sort `exports` by default

[michaelfaith]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Expected

Since #918 is stuck on stuff that's unrelated to this bug, I thought it would be best to open this separate from #928, which introduces a completely new sort order algorithm for exports. Until that issue is sorted (whomp whomp), we should at least remove exports from the default sorting algorithm. It's almost never appropriate to blindly sort exports in that way.

Actual

Shouldn't sort exports

Additional Info

No response

[michaelfaith]

Actually, looking at the current behavior, it seems ok to me. It only sorts the top level keys, which should be relative entry point paths.

[anomiex]

If the top-level keys are . or start with ./, it's safe to sort them. If they don't, it's probably not.

In other words, you can sort this

  "exports": {
    ".": {
      "import": "./index-module.js",
      "require": "./index-require.cjs"
    },
    "./foo": {
      "import": "./foo.mjs",
      "require": "./foo.cjs"
    },
    "./bar": {
      "import": "./bar.mjs",
      "require": "./bar.cjs"
    }
  },

or this

  "exports": {
    ".": "./index.js",
    "./foo": "./foo.js",
    "./bar": "./bar.cjs"
  },

but not this (see also this)

  "exports": {
    "import": "./index-module.js",
    "require": "./index-require.cjs"
  },

P.S. If someone is running into problems with the last one getting sorted, they could rewrite it like this instead to avoid the problem:

  "exports": {
    ".": {
      "import": "./index-module.js",
      "require": "./index-require.cjs"
    }
  },