feat(resolve): only use exports field when defined in package.json

[aleclarson]

Description

Match how Node's resolution algorithm works and only consider pkg.exports when it's defined.

From the Node docs:

The "exports" field provides an alternative to "main" where the package main entry point can be defined while also encapsulating the package, preventing any other entry points besides those defined in "exports".

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[bluwy]

Looks like this fixes the svelte node condition issue I stumbled on recently, where pkg.module was preferred over pkg.exports because the latter ended with .mjs. I can add some tests for this soon.

[aleclarson]

@bluwy awesome! 🧇

[aleclarson]

Merged into #10504

[bluwy]

Sorry I never got to writing the tests 😅

[aleclarson]

Sorry I never got to writing the tests 😅

Honestly, I totally forgot about this PR, so no apology required :)