Soft-NPM-publish merges to main under secret package name about capi

[harrysolovay]

No. The package would be public, but under a tmp name & not advertised anywhere.

[tjjfvi]

npm install 8c39847d-47b8-464e-998e-232d5370f7bb

[tjjfvi]

The published package should have its source in a deno or similar directory such that deno users can access it via https://unpkg.com/the-npm-name/deno/mod.ts

[harrysolovay]

Currently, any publish is manual. We’re not incrementing the version/doing the publish in CI. I plan to write a little workflow that does this upon merges to main. This will spare us the inconvenience during development.

[tjjfvi]

People can also install from a git URL, which might be easier to set up

[harrysolovay]

The repo is still private. Might be an obstacle.

[tjjfvi]

secret package name

Wouldn't the package be private as well?

[harrysolovay]

A most elegant name!

[tjjfvi]

This is publishing under the-temporary-super-secret-name, so I believe this issue can be closed

[harrysolovay]

No longer relevant