Matthew Miller

I've got a sample prf tester HTML doc in a gist that has seemed to survive scrutiny so far (or maybe it's the reason why people are doing prf incorrectly...

**From WG Meeting @ 7/17:** Examples of using PRF seem more applicable as either test vectors or as externally produced documentation. Let's bucket this as something to address as part...

I'm in a similar situation, which is blocking testing of the otherwise successfully dnt-generated output. **./deno.jsonc** ```jsonc { // ... "imports": { "@std/assert": "jsr:@std/assert@^1.0.7", // ... }, "workspace": [ "./packages/server",...

@dependabot rebase

From WG Meeting @ June 11: We will need to review and discuss this more intentionally before further action is taken. Leaving in L4 for now.

GitHub has something official about publishing to NPM: https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages#publishing-packages-to-the-npm-registry

@alexz707 Please create an issue next time. Anyway I don't know what you mean, NPM has the latest of both the browser and server libraries:  There's no "[email protected]" because...

Good news, I've got library publication for both server (#725) and browser (#727) worked out as GitHub Actions workflows. It took a few tries last night but I got publicly-accessible...

I've published v13.2.2 of everything using the new GitHub Actions workflows. Look for the "Built and signed on GitHub Actions" badges at the bottom of package pages on JSR and...

From WG Meeting @ June 11: We will need to review and discuss this more intentionally before further action is taken. Leaving in L4 for now.