fix(optimizer): browser field bare import (fix #7599)

[smeng9]

Description

Closes #7599
fixes #4798
fixes #7301
fixes #7576

Additional context

Make vite correctly resolve bare imports with browser field

In #8706 @sapphi-red mentioned we need to

solved by fixing implementation around idToPkgMap

instead of the way in #8709

---

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.

[sapphi-red]

Thank you! I confirmed that #4798, #7301, #7576 will be fixed by this PR.

[sapphi-red]

Some nitpicks

[aleclarson]

As a note to anyone else who's equally as curious in the future as me, this is the "bare id mapping" in the browser field.

[customautosys]

Hi, I am having a problem with the browser field still.

When I import @xenova/transformers, it is trying to import the node modules of onnxruntime-node and sharp, which are native node modules and should not be imported in the browser. When they are imported, it creates a lot of errors due to missing node modules.

The browser field in package.json of https://github.com/xenova/transformers.js specifically states false for these modules and they should be ignored when running @xenova/transformers in the browser.

Is there any way to fix this?