Hacker News new | ask | show | jobs
by embedding-shape 34 days ago
Read the context first. Initially, we had HTML + JS pages where one function can have one error, and the page keeps on working, because the error didn't block the entire screen.

Now we have some popular framework/library that instead seems to surface these errors that aren't sitting in the top-level scope of the JS application, yet the errors ends up blocking the entire application.

That means it's bad, yes. And it's not any language, we're specifically talking about JS in browsers here.
1 comments
rune-dev 33 days ago
Modern JS frameworks can absolutely catch and isolate errors. In those cases you’d only see the error in the specific component that had the error. Or if they’re a good dev you as a user won’t even know! You’ll see fallback content.

An error blocking the full screen is a failure on the developer not the tools.

link
embedding-shape 33 days ago
> An error blocking the full screen is a failure on the developer not the tools.

I don't see how this is possible, given that the default experience with HTML and JavaScript isn't "Tear down the entire page to display an error", but something that's seemingly becoming more and more common to actually come across. Guess I need to chase down what library/framework this is coming from, since seemingly I'm not able to describe the issue properly.

You don't need the "modern JS framerwork" to "catch and isolate errors" because that's a feature JavaScript comes with by default in browsers! You literally have to add code to make it worse, which seems to be happening in some framework/library.

If you're manually adding logic for doing "error in component doesn't break entire application" then you're already working against what the environment gives you by default for free.

link