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

nextline-web

v1.0.11

Published

[![npm](https://img.shields.io/npm/v/nextline-web)](https://www.npmjs.com/package/nextline-web) [![Unit tests](https://github.com/simonsobs/nextline-web/actions/workflows/unit-test.yml/badge.svg)](https://github.com/simonsobs/nextline-web/actions/workflow

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tai.sakumatai.sakuma

Keywords

Readme

nextline-web

npm Unit tests Test Status

Web frontend for Nextline.

Nextline lets multiple users execute concurrent Python scripts line by line remotely from the browser.

The backend API is provided by separate packages (e.g., nextline-graphql).

Screenshot

Screenshot

How to run the Nextline frontend web app

The section shows how to run the Nextline frontend web app. To start, you need to know the URL of the backend API server.

As a Docker container

Docker images of the Nextline frontend web app are created as ghcr.io/simonsobs/nextline-web.

Environment variables in the container

You can configure the web app in the container with these variables.

| Environment variable | Default value | Description | | -------------------- | ----------------------- | ------------------------------------------ | | PUBLIC_PATH | / | Path in the URL of the web app | | API_HTTP | http://localhost:8000 | URL of the GraphQL API server | | API_NAME | localhost | Text to be shown as part of the title | | SEED_COLOR | #607D8B | The source color (hex) of dynamic colors* |

*Accessible colors in light and dark modes are dynamically generated by Dynamic Color in Material Design.

For example, if you are to run the web app at the port 8080 with the path /nextline/ and use the GraphQL API server at http://localhost:5000/graphql as the name API 1, you can do so with the following command.

docker run -p 8080:80 -e PUBLIC_PATH=/nextline/ -e API_HTTP=http://localhost:5000/graphql -e API_NAME="API 1" ghcr.io/simonsobs/nextline-web

If you are on the localhost, the web app is running at http://localhost:8080/nextline/.