lucamug

Interesting. So I guess the solution is to add a filter to the watcher so that it ignores these files.

Take your time. For the moment I just added a space between `{` and `-` (that is still valid CSS) 😊

This issue has a workaround described here, in case anyone need it: https://package.elm-lang.org/packages/NoRedInk/noredink-ui/latest/ ``` npx -p [email protected] elm bump ```

Same as https://github.com/elm/compiler/issues/2171 This issue has a workaround described here, in case anyone need it: https://package.elm-lang.org/packages/NoRedInk/noredink-ui/latest/ ``` npx -p [email protected] elm bump ```

This may be redundant (https://stackoverflow.com/questions/9254891/what-does-content-type-application-json-charset-utf-8-really-mean/9254967) but maybe good to have? (https://portswigger.net/research/json-hijacking-for-the-modern-web)

Yes, sometime package authors add example that also include the imports, but it is not always the case, so I think an example generated automatically could be a safer approach....

@cmditch, > How have you addressed the problem in the meantime? Some workaround seems available at https://github.com/elm/virtual-dom/issues/103

> Anyone have a fork with this fixed? Been dealing with this same issue as well. At work we use `elm-go`, a clone that we made to fix some issues...

Is this for all OSs?

Adding a note on the website https://elm-ui.netlify.app/ would help. I think that is the major source of confusion, more than the git repository.