Fix package.json exports order

[jjspace]

Description

Apparently the order of keys in the exports object matters:

Within the "exports" object, key order is significant. During condition matching, earlier entries have higher priority and take precedence over later entries. The general rule is that conditions should be from most specific to least specific in object order.

It's very bizarre to me that key order matters in an object not an array but apparently it does. esbuild now seems to warn about it which is why I noticed:

This PR just fixes that order and the warnings are gone. I don't think this changes our build and if I understand it correctly I don't think it should change downstream users but would appreciate someone double checking me on that.

Issue number and link

No issue

Testing plan

1. git clean -dxf
2. npm install
3. npm run build
4. Make sure there are no warnings

Author checklist

• I have submitted a Contributor License Agreement
• I have added my name to CONTRIBUTORS.md
• I have updated CHANGES.md with a short summary of my change
• I have added or updated unit tests to ensure consistent code coverage
• I have updated the inline documentation, and included code examples where relevant
• I have performed a self-review of my code

[github-actions]

Thank you for the pull request, @jjspace!

✅ We can confirm we have a CLA on file for you.

[ggetz]

Thanks for the fix @jjspace!