Can the convex components switch to better lint tools like biome, that would catch errors better.
I've constantly run into issues every time I attempt to use a convex component. I'd recommend the convex components switch to biome, and strict type checking with verbatimModuleSyntax.
I currently have an error that the only way around is to bypass CI checks to get this in(which we hate to do). Or have my team wait until a fix is pushed. These types of type-errors are 100% avoidable with a stricter type check and lint setup.
In my case, as seen in the screenshot below, since our project is a monorepo. one breaking step breaks all the others. In this case, my attempt to use the convex rag component. Now my only choice is to bypass checks to get this in. Submit an issue or fork the repo and put up a PR, and have my team wait for this to get in.
This issue is evident in various convex components I've tried. Including the convex rag, agent, r2, workpool, etc. and has made it so we just generally are not able to use them in our codebase.
See screenshot of both my blocking issue in the rag component. And a simple fork of the agents components with tons of type and lint errors.




1 Reply
I don't get it, why is Biome running in component code? Shouldn't it ignore dependencies?