If you use a build tool that includes type checking along with bundling (e.g. webpack + ts-loader without transpileOnly, create-react-app), do you do so only on build or also during development? Why not just run tsc/flow as a separate build step in CI, and in your IDE for dev?
-
Show this thread
-
Replying to @devongovett
The bundler is typically the second thing, after their editor, that gives a developer insight to the validity of their code. For that reason it makes a lot of sense to consider the bundler as your development environment. For production it doesn't really make any sense.
1 reply 0 retweets 2 likes -
Replying to @sebmck
i.e see errors in both editor AND terminal/browser console? But maybe not block the build so you can hack and fix errors later? Seems duplicative to me... I would have thought people wanted it the other way: block build in production for linter/type errors.
2 replies 0 retweets 0 likes -
Replying to @devongovett
People who want it to block production builds will just run their lint command before. Not everyone has their editor configured correctly for a project, errors may not necessarily be shown, it's an additional way before their changes hit CI and they release they needed to run X.
3 replies 0 retweets 5 likes
create-react-app has good prior art for showing lint errors as a seamless part of the packaging experience. I don't know where I fall on the spectrum of ignorable errors since I'm undecided if there should even be separation between "warnings" and "errors".
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 