Renamed to elm-messenger/messenger-extra. That is where the repository lives now. It has not been published as a package under the new name.
Versions published as linsyking/messenger-extra still install under that name. 12 versions of 20 come from the new location (see their notes).
Rerouted (renamed, verified). The GitHub user or repository was renamed. The tag is still there, at the new name. The Lamdera package server serves a copy recovered from https://github.com/elm-messenger/messenger-extra.
What we checked: The repo moved to github.com/elm-messenger/messenger-extra. Rebuilt with git archive from commit de079ad35823 of https://github.com/elm-messenger/messenger-extra (zip prefix linsyking-messenger-extra-4b6aad9/, America/Los_Angeles times): the zip is byte-identical to the one package.elm-lang.org recorded, SHA-1 0d5f2957151f79ab7f726c12594498518e2021bf.
The Lamdera compiler uses this copy and prints a one-line notice saying so. elm itself fails to download this version.
Details · package.elm-lang.org's zip: https://github.com/linsyking/messenger-extra/zipball/1.2.1/
These are components that might be provided by an elm package.
There are some limitations for portable components:
Portable Component Message Codec
Portable Component Target Codec
You can generate a general type of component from a concrete portable component, which means you can manage this component with a list of user components.
Generate abstract component from concrete component.
Portable component init type sugar
Portable component update type sugar
Portable component updaterec type sugar
Portable component view type sugar
Portable component storage as a specific component type sugar
ConcretePortableComponent
Used when createing a portable component.
Use
translatePortableComponentto create aConcreteUserComponentfrom aConcretePortableComponent.The
scenemsgtype is replaced by()because you cannot send changescene message.