Open ponahoum opened 1 year ago
+1 To this, I also would like to be able to run multiple instances of the typescript checker to typecheck two different builds needed for running a figma plugin. I noticed there were some changes in the proposed 0.7 release, would those changes make this possible?
I have a similar situation. Here's the structure:
apps/
`-- example
|-- eslint.config.js
|-- package.json
|-- src
|-- tsconfig.json
`-- vite.config.ts
libs/
`-- name-lib1
|-- eslint.config.js
|-- package.json
|-- src
|-- tsconfig.json
`-- vite.config.ts
Development mode starts from apps/example. But at the same time, I would like ESLint to show errors in the library because they are being developed simultaneously. Please advise on what I should look into, if this is possible.
Is your feature request related to a problem? Please describe.
We have a monorepo with a /frontend and /backend folder. Of course, vite-plugin-checker is installed and setup within /frontend. I'd like to have multiple instances of vue checker to have both my frontend and backend lint errors to show when opening my web browser. This would be extremely valuable for my project development approach, which is fullstack
Describe the solution you'd like
Either:
Describe alternatives you've considered
I've tried using the concurrent package to run both eslint commands as well as the && operator (to run eslint command twice, one for each folder) but it fails for some obscure reason. I feel like the eslint argument is parsed in a way that doesn't allow to put any kind of command in the "lintCommand" option.
Additional context
No response
Validations