Probably Elm using
It makes a lot of sense to me too. I think Elm is unusual in having the compiler and packaging system to tightly bound together. But still, in the first instance my aim is to do it without a special compiler version, or breaking any existing system.
I write a lot of packages and have packages that depend on others. Its frustrating developing and having to switch things in and out of the
src list in
elm.json, and of course adjust the transitive dependencies as you do it. Quite a few times, I’ve just published a package that is a work in progress, just so I can use it in another project I am working on it, as that can be the easiest way.
I’d be interested in being able to support versions < 1.0.0 to help with that. But that seems unlikely to work with the compiler.
I can always publish a private package to
my-project-alpha 1.0.0, and bump it as many times as needed during development, then publish as
my-project 1.0.0, once its ready. – Added this as an example in the Gist.