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

shift-wasm

v0.0.3

Published

WebAssembly runtime for Python, Lua, Ruby and etc.

Readme

shift-wasm

WebAssembly runtime for Python, Lua, Ruby and etc.

Online demo: https://shift.js.org/

Install

npm install shift-wasm

Usage

| Language | WASM File | Data File | | :- | :- | :- | | Python | shift-wasm/assets/python.wasm | shift-wasm/assets/python.data | | JavaScript | shift-wasm/assets/qjs.wasm | | | Lua | shift-wasm/assets/lua.wasm | | | Bash | shift-wasm/assets/bash.wasm | | | Ruby | shift-wasm/assets/ruby.wasm | | | Scheme | shift-wasm/assets/chibi.wasm | shift-wasm/assets/chibi.data | | C | shift-wasm/assets/picoc.wasm | |

Examples in Vite and React environments:

import { useEffect } from "react"
import { makeConfig, python } from "shift-wasm"

// get location of .wasm and .data files
import wasm from "shift-wasm/assets/python.wasm?url";
import data from "shift-wasm/assets/python.data?url";

function App() {
    useEffect(() => {
        // the code to run
        const code = "print('hello world')";

        // callback to get result
        const fn = (text:string) => (document.querySelector("#output") as HTMLElement).innerText = text;

        // run the code
        python(makeConfig(code, fn, wasm, data));
    })
    
    return <pre id="output"></pre>
}

export default App

Different build tools use different ways to get location of .wasm and .data files.

Additionally, you may need to exclude ws, for example, vite and rollup:

import { defineConfig } from 'vite'

// https://vite.dev/config/
export default defineConfig({
  // ...
  build: {
    rollupOptions: {
      external: ["ws"],
    }
  },
})

Usage via external module

<html>
    <body>
        <!-- Create a element to display output -->
        <pre id="output"></pre>
        <script type="module">
            // Load module
            import python from "https://shift.js.org/wasm/python.js";           // interpreter runtime
            import makeConfig from "https://shift.js.org/wasm/common.js" ;      // interpreter config

            // the code to run
            const code = "print('hello world')";

            // callback to get result
            const fn = (text) => document.querySelector("#output").innerText = text;

            // run the code
            python(makeConfig(code, fn));
        </script>
    </body>
</html>

makeConfig in external module is different from this package, it does not need the wasm and data parameters.

Refer page in <iframe>

<html>
    <body>
        <!-- iframe to display shift -->
        <iframe id="code" title="Shift" style="width: 100%; height: 600px; border: 0;"></iframe>

        <script>
            const lang = 'lua';                     // language
            const input_text = '';                  // data of STDIN
            const code_text = 'print("hello")';     // code to run

            // generate URL
            const input = encodeURIComponent(btoa(encodeURIComponent(input_text)));
            const code = encodeURIComponent(btoa(encodeURIComponent(code_text)));
            const url = `https://shift.js.org/#lang=${lang}&input=${input}&code=${code}`;
            
            // set iframe src
            document.querySelector("#code").src = url;
        </script>
    </body>
</html>