How do you handle runtime exceptions caused by extensions?

supermario · July 19, 2020, 7:59am

This has been raised before, this thread has lots of good discussion, workarounds and references:

Also this:

elm/browser/blob/master/notes/navigation-in-elements.md

# How do I manage URL from a `Browser.element`?

Many companies introduce Elm gradually. They use `Browser.element` to embed Elm in a larger codebase as a low-risk way to see if Elm is helpful. If so, great, do more! If not, just revert, no big deal.

But at some companies the element has grown to manage _almost_ the whole page. Everything except the header and footer, which are produced by the server. And at that time, you may want Elm to start managing URL changes, showing different things in different cases. Well, `Browser.application` lets you do that in Elm, but maybe you have a bunch of legacy code that still needs the header and footer to be created on the server, so `Browser.element` is the only option.

What do you do?


## Managing the URL from `Browser.element`

You would initialize your element like this:

```javascript
// Initialize your Elm program
var app = Elm.Main.init({
    flags: location.href,
    node: document.getElementById('elm-main')
});

This file has been truncated. show original

Topic		Replies	Views
Runtime errors caused by Chrome extensions Request Feedback	19	4605	October 14, 2019
Runtime errors with rtfeldman/elm-css and Dark Reader Request Feedback	3	1202	May 27, 2019
Why do I get a runtime error Learn	7	1494	March 23, 2019
Breaking DOM generates endles stream of runtime errors Learn	7	547	February 14, 2021
Elm app not compatible with ChromeVox screen reader Request Feedback	7	1225	June 3, 2019

How do you handle runtime exceptions caused by extensions?

Related topics