Conclusion: Jest + TypeScript + ESM is absolutely cursed. Don’t go down that road. - ThreadSky

ThreadSky

About ThreadSky

keithjgrant.com • 112 days ago

Conclusion: Jest + TypeScript + ESM is absolutely cursed. Don’t go down that road.

Comments

srsholmes.com•112 days ago

@vitest.dev to the rescue!

ggascoigne.bsky.social•112 days ago

Agreed, I spent an age trying to get jest and typescript and esm working, it’s a complete mess. Gave up and switched to vitest, not only was it surprisingly easy, it was hugely faster. Never looked back.

lancejeffers.bsky.social•112 days ago

The problem here is Jest specifically. Vitest handles TS + ESM smoothly, but idk if you've got a large Jest setup that cannot be easily migrated

keithjgrant.com•112 days ago

Yeah we kinda want to switch to Vite anyway, but it hasn't been a priority. This is making me think it might be worth making it one

darek.bsky.social•112 days ago

That and the requirement for JSDOM are the showstoppers for me.

tylerdotjs.bsky.social•112 days ago

Yup! ESM and the JavaScript landscape continues to be cursed. Currently attempting to stand up automated E2E performance auditing of some critical screens in our app. Trying to get some packages like playwright-lighthouse to play nicely with an ESM has been... taxing.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply