This is context for the previous post in the series, for areas I know of in programming where it makes sense to create an output distribution file.
For C, C++, Rust and Go, one might want to distribute a pre-built executable binary. I want to get into Go and so want to see a good approach for sharing my projects.
From Hello world example:
$ go build hello-world.go $ ls hello-world hello-world.go
$ cc -O -c main.c
$ cargo build
In the case of a VS Code extension (typically made in TypeScript) or a Ruby gem, one creates a zipped archive like
.gem which contains selected files to be distributed.
Then this file could be uploaded to GitHub or a provider (like VS Code Marketplace or RubyGems), so others can install your project.
For example, I create a local archive of my VS Code extension and add it to a release under Assets.
src directory of source code (e.g. TypeScript) and a
For example, here are some Vue JS files available in a
That seems to match the versioned
dist directory on GitHub.
Or you can use a single Production CDN JS file: