feat: enable optimizeDeps.esbuildOptions.loader

[dickeylth]

Description

Enable scan respect optimizeDeps.esbuildOptions.loader option so that the map of js types to loader could be customized, relevant issue: #3448

Additional context

I've read the relevant pr: #1884 and the suggested solution is "use an esbuild plugin to specify your own loaders", which I think it could be discussed because in that way the import.meta.glob logic would be missing in my own esbuild plugin. In my situation there are some internal ui library codes which have decorators in .jsx files and esbuild could only work by specify --loader:.jsx=tsx, since we have optimizeDeps.esbuildOptions in vite config I think it's acceptable to enable the build loader config to be recognized, otherwise maybe we should add loader into the omit list to avoid misleading option?

---

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]

Hi @dickeylth, I've put this in the team board to be discussed in the next meeting. Can't promise this would be talked on next though as we already had a lot in the list. Though it may be good to rebase too in the meantime. From a glance, the idea sounds fine to me.

[patak-dev]

@dickeylth we discussed the PR in today's team meeting and we think it is a good addition.

There is a debug message that should be modified to reflect the used loader:

debug(
  `Unable to parse dependency: ${id}. Trying again with a JSX transform.`
)

Once the message is corrected, and conflicts solved we can merge it 👍🏼

[dickeylth]

@bluwy @patak-dev It's been about 3 weeks, when will this pr be merged?

[bluwy]

I've cleaned it up a bit, and merged up main. I think we forgot to merge this one in, but this lgtm to merge anytime.