modules VS unpkg

If you want to read more about plans of Node.js team related to loaders, check nodejs/modules#351 issue.

It is complicated but most user anger should be directed to node.js module group[1]. TS is forced to follow node.js standard.

[1] https://github.com/nodejs/modules/issues/323

There was a bug in Node.js v13.0–13.6 where packageJson.exports["."] had to be an array with verbose config options as the first item (as an object) and the “default” as the second item (as a string). See nodejs/modules#446.

On platform that doesn't support browser extension (such as Google Chrome Android), you can run YouTube Musical Spectrum [1] using one of these bookmarklets:

javascript:import("https://cdn.jsdelivr.net/npm/@mfcc64/ytms/script.mjs")

  javascript:import("https://unpkg.com/@mfcc64/ytms/script.mjs")

{ "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json", - "changelog": "@changesets/cli/changelog", + "changelog": ["@changesets/changelog-github", { + "repo": "your-org/your-repo" + }], "commit": false, "fixed": [], "linked": [], "access": "restricted", "baseBranch": "main", "updateInternalDependencies": "patch", "ignore": [] }

CLI downloads minimized versions of htmx and hyperscript (from official and trusted unpkg.com CDN) to the ./static folder and places them as separated

And the controls seem to be made with https://github.com/timmywil/panzoom:

https://unpkg.com/: Seems to just provide the npm entry files straight up. Can’t use.