Well today I've implemented my own NPM module downloader. A very bare bones version of one though so yarn devs can still sleep well tonight.
@mariusor Neat. What was your reason for making it? :o
@mauve I wanted to limit the build pipeline for the project this is used into, to a single dialect: Go.
@mauve I'm all about about that "simple to deploy" mantra.
@mariusor That's awesome. do you have a go based JS bundler too? Or are you using raw imports somehow?
@mauve esbuild is actually written in go and can be mostly used as a library.
I had that in place since a long time ago.
@mauve the current work was done for a static site generator[1] that I'm using to publish the GoActivityPub documentation and it's used for adding some search support and for being able to enable mermaid diagrams.
Eventually the functionality will make its way into the ONI project which is a one user ActivityPub service built with Lit-JS.
But before that can happen I need to see if I need to implement the dependency resolution by myself, or there's some library that I can use - currently only the modules listen in package.json get fetched from NPM, which greatly limits the scope. :D
[1] https://git.sr.ht/~mariusor/staticman