fix(oxlint): Skip vite.config.ts which fails to import

[leaysgur]

The same as #20326

(It's fine to release this as scheduled one)

[leaysgur]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(oxlint): Skip vite.config.ts which fails to import #20327 👈 (View in Graphite)
• fix(oxlint,oxfmt): Redirect JS stdout to stderr for LSP #20321 : 1 other dependent PR (#20417 )
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[camc314]

I'm not convinced this is a good idea? Users won't see the debug log unless they have RUST_LOG=debug (basically no one), and they're going to see lint run fine, but not use their config

[leaysgur]

Thanks for the review. I may be a bit too defensive here.

Let's keep the current behavior (error) for now and see if it becomes a real issue in practice.

(Will revert the oxfmt side later.)

[leaysgur]

Just in case, I'll add more likely scenarios for the record.

• If __dirname is used in vite.config.ts even though it's a type: module project
• Vite can transparently handle CJS/ESM via vite.resolveConfig(), so no error occurs
• However, since we are using pure import(), this will result in an error

Users will see an error message to that effect, but they might wonder why.