[sibelius]

add SKIP_TYPE_CHECK env to disable typescript type checking fix #5784

When you are just testing new code, it makes sense to be less strict on type checking

This also make compilation with typescript much faster

[julioxavierr]

I agree

[deftomat]

#6406 improves type-checking a lot.

Files emitted by Babel are immediately send to browser and type-errors shows up later, when type-check finish. Also, the type-checking itself is now super fast.

We just need to wait for a release. 😉

[sibelius]

I want to keep rendering my components even with type errors

My use case is that I’m just exploring some packages and I don’t need 100% typecheck

[deftomat]

Ok, fair enough 👍

[lstkz]

@deftomat Any chance to merge this?
I can see that many people complain about the same thing. Sometimes, we draft something fast, and we want to see results quickly in the browser, but type checking prevents it.

[lstkz]

Here is an example

The app won't compile because there are unused variables. Such issues shouldn't prevent development.

[deftomat]

Well, firstly, it needs to be updated as this flag is also used here
https://github.com/facebook/create-react-app/blob/1548a0a92e41f9f626aa2c5226fb1a2cb2ec9229/packages/react-dev-utils/WebpackDevServerUtils.js#L110

Then, you can contact a maintainer as I cannot merge it 😉

[stale]

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[stephenlaughton]

This would be really great to see merged, especially developing on a resource constrained machine, having VSCode AND the dev server type-check with every save is redundant in some cases. In many cases people want to run their type-checking alongside the build step instead of inside of it.

[stale]

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[sm-tc]

Any updates on this? Can I help in some way?

We're building a multi-tenant application and at the moment each additional tenant is adding about a minute to our deploy time because tsc runs on every build. Would be awesome if we could just run it once at the start and just let babel do its thing for the builds.

[sibelius]

I've made a patch-package https://gist.github.com/sibelius/594a6b64656047e5f22f1363cd41aa87 until this lands

[mgcrea]

Most users do code using an IDE that already provide eslint/ts live error checking.

So you end up running these checking processes twice when using the CLI in development mode.

Clearly we should have this as an option, and it could make sense to make it the default.

Was always a major pain point for me, great that there is now the TSC_COMPILE_ON_ERROR and EXTEND_ESLINT to at least not stop me from hacking stuff around quickly.