JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
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.
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.
Also worth mentioning that editors will usually only show errors in the files you have open—relying on your editor for dev errors would punt some horrible problems down the road, to when you're finally ready to publish.
What about tests? Should a bundler run them for you too? Tests are another form of code checking... Where do you draw the line?
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".
yeah editor not being configured when contributing to someone else's project is a fair point
Or even my own project... le sigh
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
