Linting and type checking currently only happens when creating a build. This also happens in CI, so we will catch errors eventually, but it would be a better DX if we tightened that feedback loop.
Unfortunately, Vite seems to think it idiomatic to keep that stuff out of the build system, so it's questionable how we want to implement it. This position is supported by vite-plugin-eslint being all but dead, basically. There is vite-plugin-checker, which Vite also mentions on their website, but I haven't looked into it, yet.
Of course we could also provide IDE integration (if todays IDEs aren't smart enough to pick up on the ESLint config already anyway) or custom scripts as npm-scripts or like we do in Tobira. 🤔
Linting and type checking currently only happens when creating a build. This also happens in CI, so we will catch errors eventually, but it would be a better DX if we tightened that feedback loop.
Unfortunately, Vite seems to think it idiomatic to keep that stuff out of the build system, so it's questionable how we want to implement it. This position is supported by
vite-plugin-eslintbeing all but dead, basically. There isvite-plugin-checker, which Vite also mentions on their website, but I haven't looked into it, yet.Of course we could also provide IDE integration (if todays IDEs aren't smart enough to pick up on the ESLint config already anyway) or custom scripts as npm-scripts or like we do in Tobira. 🤔