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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pytincture/runtime

v0.9.27

Published

Standalone pytincture.js runtime with inline app auto-start support.

Downloads

122

Readme

@pytincture/runtime

Standalone build of pytincture.js, the Pyodide bootstrapper used by the pytincture framework. It can be loaded directly from a CDN to run embedded Python snippets (or zipped pytincture apps) with no backend.

Usage

<!DOCTYPE html>
<html>
  <head>
    <script src="https://cdn.jsdelivr.net/npm/@pytincture/[email protected]/dist/pytincture.min.js"></script>
  </head>
  <body>
    <div id="maindiv" style="width:100%;height:100vh;"></div>

    <script type="text/json" id="micropip-libs">
      ["faker"]
    </script>

    <script type="text/python">
from dhxpyt.layout import MainWindow

class Demo(MainWindow):
    def load_ui(self):
        self.set_theme("dark")
        print("Demo loaded!")
    </script>
  </body>
</html>

What happens:

  • The runtime loads Pyodide (default https://cdn.jsdelivr.net/pyodide/v0.28.0/full/).
  • Installs micropip and any extra wheels listed in #micropip-libs.
  • Installs the default widget library (dhxpyt) or another package you configure.
  • Auto-detects <script type="text/python"> blocks, mounts them under /appcode, finds a MainWindow subclass (or explicit entrypoint), and runs it.
  • Errors are printed to the console and rendered inside #maindiv when present.

Configuration

Before the script tag loads, you may set the following globals:

<script>
  window.pytinctureAutoStartConfig = {
    widgetlib: "dhxpyt",
    libsSelector: "#micropip-libs",
    pyodideBaseUrl: "https://cdn.jsdelivr.net/pyodide/v0.28.0/full/",
    enableBackendLogging: false
  };
  // Disable auto-start if you want to call runTinctureApp manually:
  // window.pytinctureAutoStartDisabled = true;
</script>
<script src="https://cdn.jsdelivr.net/npm/@pytincture/runtime/dist/pytincture.min.js"></script>

Manual start (if auto-start is disabled):

runTinctureApp({
  mode: "inline",
  widgetlib: "dhxpyt",
  enableBackendLogging: false
});

Development

This package lives inside the main pytincture repository:

cd pytincture/frontend
npm install
npm run build        # emits dist/pytincture.{js,min.js,esm.js}
npm run build:watch  # rebuild on changes

npm run build automatically syncs the package.json version with the Python framework (pytincture/__init__.__version__), so npm releases always match the backend version.

Publishing

From the repo root you can run:

bash scripts/publish_runtime.sh

The helper script:

  1. Reads the framework version.
  2. Installs dependencies & syncs package.json.
  3. Builds the bundles.
  4. Publishes to npm if that version isn’t already available.

Once published, load from jsDelivr/UNPKG:

<script src="https://cdn.jsdelivr.net/npm/@pytincture/[email protected]/dist/pytincture.min.js"></script>

Replace 0.9.20 with the framework version you need, or omit it to use @latest.