And on a related node, recently publish packages can be replaced with gleam publish –replace. This is useful for correcting any mistakes made during the process of releasing a package.
Does that mean the content of a particular version of a package can change? (Also I think there’s a typo “recent published packages”?)
This is a feature of Hex (a package manager for all BEAM modules (erlang, elixir, gleam, etc)). The time limits are quite short so there should be very little danger:
There are exceptions to the immutability rule, a package can be changed or unpublished within 60 minutes of the package version release or within 24 hours of initial release of the package.
This all sounds really great, except this bit:
Does that mean the content of a particular version of a package can change? (Also I think there’s a typo “recent published packages”?)
This is a feature of Hex (a package manager for all BEAM modules (erlang, elixir, gleam, etc)). The time limits are quite short so there should be very little danger:
https://hex.pm/docs/faq#can-packages-be-removed-from-the-repository
That’s neat !
I wish PyPI had this: these kind of small release mistakes can happen very easily.
Ahh ok. The time limits make it a bit less concerning.
Packages also come with checksums so the tooling will identify a change compared to what is expected in the lockfile.
While we’re pointing out typos: s/related node/related note
Isn’t a TypeScript declaration file supposed to be .d.ts, not .ts.d? For example.
Oops, typo. Thanks for catching that.
There’s a few more of the same one.
haha I was so confused by this and was thinking “what kind of workaround is this???” 😅 glad to know it was just a typo
Gleam looks like a very nice language: I hope to find time to give it a try this summer.
Is there a showcase of “stuff built with Gleam” out there ? I’m curious :)
There’s a list of libraries and projects here: https://github.com/gleam-lang/awesome-gleam
Could be useful. More to come in future!