chore: Publish v2 as alpha

[Zearin]

I arrived here from diving into htest-dev/htest.

In that repo’s render.js file, it imports from https://html.htest.dev/src/util.js. And inside that file, it has the following lines at the top (after 1 import):

export { default as create } from "https://v2.blissfuljs.com/src/dom/create.js";
export { default as bind } from "https://v2.blissfuljs.com/src/events/bind.js";
export { default as include } from "https://v2.blissfuljs.com/src/async/include.js";

So hTest is using some code from v2 of Blissful, but v2 isn’t available on npm.

If v2 is good enough for @LeaVerou to use in another young project (hTest), it’s probably good enough to publish as an alpha version to npm.

Semantic Versioning will protect current users from accidentally updating to an alpha version. Users won’t accidentally end up with the alpha code unless they deliberately opt-in to it.

Whaddaya say? 😸

[LeaVerou]

I'm fine with it (IIRC v2 is ready except docs, so that should be fine for an alpha). But also, gah, we should not have a dependency on this in hTest.

[LeaVerou]

I just looked at the current state and started a checklist here: #264
Any interest in picking some of these up @Zearin ?

[Zearin]

I think so. Let me give it a shot.