Deno2 updates

[jimmont]

first/preliminary pass at update related to deno v2, fixing #91

• bundle script and task added
• test of distributable and task for it added
• global for window updated
• jsr imports for latest versions updated, with comments for as it was unclear why previous attempt was reverted related to this and what might be done about those things, whatever they might be
• tests pass

[emrahcom]

Is window or globalThis needed for crypto.subtle.generateKey?
It should work without them.

[timonson]

Is window or globalThis needed for crypto.subtle.generateKey? It should work without them.

Using crypto.subtle.generateKey directly can lead to issues if crypto or subtle has been shadowed in the local scope, causing unexpected failures. Opting for globalThis.crypto.subtle.generateKey ensures explicit clarity and better compatibility across diverse environments, avoiding confusion in larger codebases or contexts where crypto isn't globally available.

[timonson]

Looks good to me. Can you tell me if I have to configure something on the jsr website for that?

[jimmont]

@timonson I added the fields for publishing to jsr per https://jsr.io/docs/publishing-packages and deno publish --dry-run looks ok. Please check the version and exports fields in the last change to deno.json.

If possible I'd prefer to leave the publish and version change to you or whomever wants to publish this new version, so feel free to make those changes when ready and without my help--the field in deno.json is simply "version". I guessed a major version bump simply because I'm unsure how backward compatible this is for deno v1, etc.

Hope this helps.

It's also worth noting that if you have hesitations related to using jsr it's also possible to publish this here via github using a raw.githubusercontent.com or gh-pages url. I think this might be the most flexible option if browser support is important. I haven't looked closely into the pros and cons of using jsr.

[jimmont]

my brief checks of the ci failures suggests deno upgrade is needed, denoland/fresh#2622

I'm beginning to think publishing to jsr may not be in line with the compatibility goals here, and simply publishing here on gh, or similar, and on deno.land/x/. More elaboration in the jsr-feedback deno discord here (2024-11-21) https://discord.com/channels/684898665143206084/1203185670508515399/1308971117968621589

fwiw I'd recommend closing this PR and sticking with deno.land and perhaps also http://raw.githubusercontent.com or gh-pages if a live demo in the client is wanted. Hope this useful. If I can help more just let me know.