Packaging a finished project

[ariankordi]

I’m thinking of having this ambitious project in Fusion with multiple source files, tested across many of the target languages, intended for others to use.
When it comes time to make this available to the world, what are the recommended steps for publishing it?

I don’t want everyone to have to copy the transpiled output into their repo, so that searching GitHub yields like 20 different copied versions of the library over time. They should be able to nicely import it.

Should I commit to publishing it across all package managers? (npm, PyPI, NuGet, Maven/Gradle…)? Should I expect people to pull it in as a git submodule? Should it be installable from the git repo directly without publishing (not supported by NuGet)? Should I have a separate repo or branch for releases? What if I don’t care about or don’t test languages like D, Swift, Java?

There’s so many questions and I’m curious to hear what the thoughts are.

[pfusik]

There is nothing in Fusion that aids in packaging and distributing your code. I think you should do whatever feels best if you authored the library in each target language (i.e., publish on npm etc). This might sound like a lot of work, but from my experience publishing my projects, it's mostly a one-time investement for the first version - the updates are much easier. For C and C++, one expects that your project builds and installs from sources (and you might release binary builds as a bonus).
For languages you don't care, just don't transpile to them, but consider adding a sentence in your README that they might work with some effort if someone's interested.
In my projects, I orchestrate the transpilations and builds from a Makefile. Packaging all the different targets should be as simple as a version bump and make dist. You might even go with Continuous Delivery, but I have no experience with that.