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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@bscript/lang

v2.0.0

Published

A CLI for BlueScript

Readme

Run BlueScript on 64bit-Linux (or macOS) systems

Requirement

  • node.js

  • The cc command for compilation of C programs

Installation

Download BlueScript from GitHub:

git clone https://github.com/csg-tokyo/bluescript.git

and install it.

npm install

Move to the ./lang directory.

cd lang

Run the REPL

To run the REPL (Read-Eval-Print Loop) of BlueScript,

npm run shell

Built-in utility functions print(v: any), print_i32(v: integer), and performance_now() are available.

To close the shell,

> .quit

To read a source file and run its content,

> .load foo.bs

This reads foo.bs and runs the BlueScript program contained in that source file.

The source files can be given as command-line arguments.

npm run shell foo.bs bar.bs

This reads and runs foo.bs and bar.bs in this order when the REPL starts running.

Note that the REPL separately compiles every code fragment by users. It performs the reading, compiling, running, and printing loop. All the temporary files are stored in ./lang/temp-files.

Compile a BlueScript program

To compile a BlueScript program,

npm run compile foo.bs bar.bs

This compiles foo.bs and bar.bs and generates the native binary, which first runs foo.bs and then bar.bs. If a function called in foo.bs is defined in bar.bs, a compilation error will be reported.

The compiled programs can access the same built-in functions as the ones available in the REPL.

To give an optional argument to the backend C compiler,

npm run compile foo.bs bar.bs -- -args=-g,-o,foo

Arguments specified with -args= are passed directly to the C compiler. Commas within the argument string are automatically replaced with whitespace to separate individual compiler options. For example, the input -args=-g,-o,foo results in the compiler receiving the arguments -g -o foo.

Alternatively, use +args= without the -- separator.

npm run compile +args=-g,-o,foo foo.bs bar.bs

For debugging, pass the -g or +g option to the compiler. This prevents the compiler from removing working files such as generated source files in C.

npm run compile foo.bs bar.bs -- -g -args=-g,-o,foo