npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@pyscript/sw

v0.0.1

Published

PyScript Service Worker

Downloads

2

Readme

@pyscript/sw

PyScript Service Worker


Documentation

This module provides a single, standalone, script able to bootstrap a Service Worker which can drive a whole site via Python code.

Please note the file must be available locally and it must not be loaded as a module, as a Service Worker is not a module.

Example

This is the bare minimal example of an index.html file at the root of the site.

<!doctype html>
<script src="./pyscript.sw.js"
        handler="./handler.py"
        config="./handler_config.toml"
        scope="."></script>
  • src is where the PyScript Service Worker is located.
  • handler is where Python code is located. This must provide a handle_request method that will be invoked per each browsing fetch operation. Such method should return a [body, status, headers] tuple where body is the content of the page, status is its HTTP status and headers contain the content-type or any other useful header.
  • config is an optional attribute that indicates packages to load, files to fetch, and all other usual py-config goodness.
  • scope (advanced use-case) is an optional attribute that indicates where the Service Worker operates. By default it operates from the same folder, and any subfolder, the pyscript.sw.js is.

How to update handle_request

Because the Service Worker, once activated, will persist over any further session, it is pretty hard to change its operating handler.

To do so, there are two options:

  • unregister the Service Worker, clear all browsing data per that domain and hard-refresh the browser
  • change and save your handler.py file and, once saved, reach the /pyscript.sw/update_handler via browser, or run the following code in console:
fetch('/pyscript.sw/update_handler')
  .then(b => b.text())
  .then(console.log, console.error);

This operation will be intercepted behind the scene and the new file will be parsed.

The result should be an OK response, with status 200, or an error message with status 500 handled by the console.error or visible within the page once reached.