Hacker News Reader

Comment by davidy123 | Hacker News Reader

I'm going to keep hitting reload on this page until someone solves some of the worst problems of my work life right now; getting a npm monorepo with typescript, eslint and jest working smoothly. Thank you to whoever(s) that is. I'm trying to make a public project, but building/developing with it is successive layers of sometimes-works voodoo that have nothing to do with the project goals. Somewhat compounded when members of nx (nee lerna) popped in to try to help, adding another layer of sometimes-works. As it is, DX depends on a fast computer to basically rebuild the whole thing each time, or running build & test in a dozen workspaces, because I haven't found any other reliable "workflow."

View on HN

This is the current setup I'm using for my TypeScript monorepo: https://github.com/tommyguo/node_monorepo. I tried avoiding Lerna because I didn't feel like I needed it. Happy to hear feedback!

Thank you, I will take a look after current sprint.

We gave up and switched to vitest.

+1 for vitest :D I was amazed that it "just worked" after struggling for hours getting jest to work because of silly file extension problems (really... what's up with that... wouldn't that be easy to fix if the Node.js and Typescript teams would talk for 5 minutes and agree on one approach?)

I don't use Vite though. Aside from typescript, I'm trying to be as vanilla/unopinionated as possible, using Web Components for example. And there are hundreds of Jest tests I don't want to port.

You can use vitest like a standalone testing tool, it will install vite as dev-dependency but you don't need to build your whole project around vite.

In my case it was literally a drop-in-replacement for jest, done in two minutes and without a config file. A simple config file only was required a bit later when I added test- and coverage-reporting as junit.xml and cobertura format for Gitlab CI.

Didn't even have to change a single line of testing code (I didn't use Jest's mocking magic in that project though).

Thank you, it sounds pretty good, especially solving the modules problem. I will look into it when finished current sprint.

Just wanted to say thanks for this recommendation. I'm not finished yet, but it seems like a huge improvement over all the wtf of jest, along with a lot of new niceties.

Maybe I spoke too soon, cyclical imports problem seems pretty big.

oh yeah, and this esbuild keepNames nonsense has lost me some hair.

We dropped Jest and switched to Vitest across the entire stack. It's a shame what happens to these projects over time...

Reply on news.ycombinator.com