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

The current way that doesn't require/neednpm and/orNodeJS to fetch the package is:

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

After that, usinguntar /gz brings in thepyscript folder with apackage one that contains in it thedist which is what any user is after.

Issues with all approaches

• npm usessemver, notcalver, 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 thenpm 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 indist into a newpyscript folder
  • copy all licenses (ours + 3rd party) into that folder
  • zip or tar.gz that folder aspyscript (TBD ... it could be namedpyscript_core too)
  • place that file in our documentation page or any place wherecalver 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