Originally derived from voidzero-dev/vite-plus#930 and voidzero-dev/vite-plus#1084
Issue with Oxlint, Oxfmt, and Oxc VS Code/LSP integration
I think it's better tracked here since it's a problem in this repo and not a problem with Vite Plus.
Currently, vp lint, vp fmt, and the VSCode extension all transparently utilize Oxlint and Oxfmt respectively.
On the Oxapps side, the ability to extract .lint and .fmt fields from vite.config.ts has been added, but they are not fully complete at present.
https://vite.dev/config/
Currently supported static config only:
export default { ... };
export default defineConfig({ ... });
Conditional and async config are NOT supported.
defineConfig(({ ... }) => ({ ... }));
defineConfig(async ({ ... }) => ({ ... }));
Since they do not know how to handle arguments.
For the first place, Oxlint and Oxfmt do not support functional config even with their oxlint.config.ts. Also, be aware that the file name, they only supports the .ts extension.
Originally derived from voidzero-dev/vite-plus#930 and voidzero-dev/vite-plus#1084
Issue with Oxlint, Oxfmt, and Oxc VS Code/LSP integration
I think it's better tracked here since it's a problem in this repo and not a problem with Vite Plus.
Currently,
vp lint,vp fmt, and the VSCode extension all transparently utilize Oxlint and Oxfmt respectively.On the Oxapps side, the ability to extract
.lintand.fmtfields fromvite.config.tshas been added, but they are not fully complete at present.Currently supported static config only:
Conditional and async config are NOT supported.
Since they do not know how to handle arguments.
For the first place, Oxlint and Oxfmt do not support functional config even with their
oxlint.config.ts. Also, be aware that the file name, they only supports the.tsextension.