lue

I just found this thread again. One example is [`Quantity.zero`](https://dark.elm.dmy.fr/packages/ianmackenzie/elm-units/latest/Quantity#zero) and [`Quantity.negate`](https://dark.elm.dmy.fr/packages/ianmackenzie/elm-units/latest/Quantity#negate): ```elm zero : Quantity number units negate : Quantity number units -> Quantity number units type Quantity number...

If you need a quick fix, try adding a type annotation to the module-level declaration. Issue seems similar to https://github.com/elm/compiler/issues/1839

To me it seems somewhat confusing to call single-variant types "or": ```elm type or Email = Email { local : Local, domain : Domain } ```

I don't think it will work but maybe you can get more information by trying to publish with [elm 0.19.0](https://github.com/elm/compiler/releases/tag/0.19.0)? At least that works for some projects with some sort...

True. FYI the new way of joining is described at https://elm-lang.org/community/slack

Another example of the same bug https://github.com/elm/compiler/issues/2252

In general, recommending imported exposed variants as well is helpful

If [turboMaCk/non-empty-list-alias](https://package.elm-lang.org/packages/turboMaCk/non-empty-list-alias/latest/) didn't already use `NonEmpty` for the same type, I'd prefer `FilledList` or `ListFilled`

I think 2 describes the code's intent better. ```elm exposing (Alias) ``` → We don't really care if this is a `type` or `type alias` ```elm exposing (Type(..)) ``` →...

The ranges are also used for the displayed error range. E.g. it's a lot nicer to mark only the `++` in `[ 1 * a ] ++ bs` instead of...