Currently we've solved for this by patching virtual-dom with an outdated / seemingly unmaintained shell script call shelm.
Unfortunately, elm-json doesn't like the "locations" key that shelm depends on to do it's overriding so every time we install or update packages that "locations" key gets deleted and the developer has to remember to bring it back after an install.
This means recently we accidentally re-introduced this Grammarly bug into a production release.
Secondarily, using shelm means that our LSP tooling using ~/.elm gets out of sync with what shelm uses for our local packages sometimes breaking intellisense.
Merging this fix means
we can remove the hacky shell script that's overriding this for us in our production builds and alleviate the incompatibility with other elm ecosystem tooling.
The patch apparently fixes issues for other "Chrome Extensions" altho we don't have any users using any of the other extensions that might also be breaking elm/virtual-dom.
Do we have an idea of what classes of browser extension issues this patch will fix? The idea looks sound to me, just want to find out if this is a full or partial solution to the issue.
This PR is a re-posting of this fix These patches fix the issue below.
Here's the expanded stack trace.
More info: https://github.com/elm/virtual-dom/pull/177#issuecomment-1125291829
Currently we've solved for this by patching virtual-dom with an outdated / seemingly unmaintained shell script call
shelm
.Unfortunately,
elm-json
doesn't like the"locations"
key thatshelm
depends on to do it's overriding so every time we install or update packages that"locations"
key gets deleted and the developer has to remember to bring it back after an install.This means recently we accidentally re-introduced this Grammarly bug into a production release.
Secondarily, using
shelm
means that our LSP tooling using~/.elm
gets out of sync with whatshelm
uses for our local packages sometimes breaking intellisense.Merging this fix means