I would pipe a faster checker as a first fail fast local and CI. I want a CI to fail fast but in the end I want it to be correct before production release

tsc caches the interface of projects so when a project is not changed, its not compiled.

see https://www.typescriptlang.org/docs/handbook/project-referen...

Yup yup, I know, but requires a lot of setup on CI. We are using project references btw. They are very cool

Why should they be different?

I didn’t know WebStorm no longer uses a custom type engine

Perhaps. In our huge project it slows the team down a bit. It could even be worth having a faster precheck / prebuilt step for the CI to fail fast. While money is less of an issue, configuring another tool in legacy monorepo might be the biggest blocker.

shameless plug

If anyone is looking for IoC + async dependency injection in react components I've made a tiny lib that does wonders for me in a an `iti+mobx` combo

https://itijs.org/docs/with-react/react-full#async-request-f... https://stackblitz.com/edit/github-3g8pzp?file=src%2FApp.tsx

Yup. Don't use react for state or some hook spaghetti like react query. Use mobx and live happily ever after :)

Exactly. Although I would go with starfx instead

Didn't know about starfx. Interesting.

To anyone reading, mobx is a more generic tool for any type of state management.

And starfx seems like a data fetching + holding state and providing hooks for that data kind of library. Very unique and looks someone cared to make something nice for that kind of problem

starfx looks interesting and innovative ! thanks for sharing

IDK, I haven't changed the react dependencies in 5 years. Everything is the same and I am happy.

next.js user? :D

I agree. It is not weird if you try to run old code through new env / vm / framework / compiler it can break.

Locking env version is important.

Double points for using experimental / POC technology like gatsby or nextjs. They are expected to burn and fail

Probably because OSI never materialized IRL and today they are all mixed up left and right and not how we “designed” and “imagined” it 50 years ago

Deepkit.io has cool validations in runtime based on TS, but it is whole another level.