Open stryaponoff opened 1 year ago
For me this happens on vite build
as soon as I activate eslint checking.
Here's my plugin config, no issues with vite build
, by the way.
checker({
typescript: true,
eslint: {
lintCommand: 'eslint "./src/**/*.{ts,vue}"',
},
terminal: true,
overlay: true,
enableBuild: false,
}),
I've made a repo that reproduces this issue. Hope it helps.
It contains two commands: yarn optimize:broken
hangs while yarn optimize:working
is working. Please note that the config files is the only difference and the only difference in configs is this plugin.
It's build over clean yarn create vite
Vue project
I'm avoiding this issue with an argv check.
import { defineConfig } from "vite";
import checker from "vite-plugin-checker";
export default defineConfig(({ mode }) => ({
plugins: [
!process.argv.includes("optimize") &&
checker({
enableBuild: false,
eslint: { lintCommand: 'eslint "./src/**/*.{ts,tsx}"' },
stylelint: { lintCommand: 'stylelint "./src/**/*.{css,ts,tsx}"' },
typescript: true,
}),
],
}));
Describe the bug
When I execute
vite optimize
command, it will never return input to user in terminal. If I disable the vite-plugin-checker, all works fineReproduction
vite optimize
in Terminal, ensure it hangsvite optimize
in Terminal, all works fineExpected behavior
The plugin should not break
optimize
commandSystem Info
Additional context
No response
Validations