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

waran

v1.2.9

Published

a compiled programming language

Readme

waran

about the project

credits

example waran program

import @io
import @math

class Program {
    method static main() {
        hello := "hello"
        waran := "waran!"

        std_out(hello waran)

        for(i := 0 | i <= 10 | i++) {

            ## skip the 5th iteration
            if (i == 5) {
                continue
            }

            std_out(i)
        }

        while(true) {
            if (counter > 10) {
                break    
            }

            std_out(counter)
            counter++
        }


        my_array := ["string value" 4738 -21.564 true]

        std_out(my_array[2])
    }
}

Program.main()

table of contents

  1. Installation
  2. Project structure
  3. Compiling code
  4. Running code

Installation

npm i -g waran

or

yarn add -g waran

Project structure

wrn init

this command will create a few folders / files:

  1. .waran folder
    • ast
    • build
  2. wrn_proj.json
    • describes the behaviour of the compiler.
      • project_info - contains general information about the waran project
      • dirs - contains paths to directories used by the compiler
        • ast_dir
          • location of abstract syntax tree (ast) files
        • wrn_proj_dir
          • location of the .waran directory (contains asts and build)
        • src_dir
          • location of the working direcotry (contains your source code)
        • build
          • location of the directory that contains built waran code
  3. src folder
    • current working directory
      • location can be modified in wrn_proj.json configuration file

Compiling code

wrn compile < .wr file location  >

this will produce a .js counterpart in the .waran/build directory unless the behaviour was modified in wrn_proj.json

Running code

wrn exec < path to .js file >

.js files can be found in the .waran/build directory with the same name as their .wr counterparts