We have various ways to obtain files needed to use PyScript offline https://docs.pyscript.net/2025.5.1/user-guide/offline/ and none of these is straight forward.

The current way that doesn't require/need npm and/or NodeJS to fetch the package is:

curl "$(curl -sS https://registry.npmjs.org/@pyscript/core/latest | jq -r .dist.tarball)" --output ./pyscript.tgz

After that, using untar / gz brings in the pyscript folder with a package one that contains in it the dist which is what any user is after.

Issues with all approaches

• npm uses semver, not calver, it's very easy to get lost with versions matching in there but also we use that channel for development purposes
• copy paste hints might not fit all users or be recommended in general
• bothering the npm registry for distribution purpose doesn't feel right, even if that's the main way most CDNs or projects use it

Proposal

• when we release, we add a step in CI that:
  • copy all content in dist into a new pyscript folder
  • copy all licenses (ours + 3rd party) into that folder
  • zip or tar.gz that folder as pyscript (TBD ... it could be named pyscript_core too)
  • place that file in our documentation page or any place where calver would provide the right package

The current bundle would be ~ 1.5MB all inclusive (as zip) so this should not be an issue but if we think it is, we could also host the artifact in GitHub when we release and point at that specific version ... all to be discussed, I've opened this to discuss indeed and/or have consensus about this way to simplify by far offline installation/use-case.

/cc @ntoll @fpliger @danyeaw