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

@allnulled/browsie-script

v1.0.0

Published

Scripting language oriented to database management.

Readme

browsie-script

Scripting language oriented to database management.

Installation

npm i -s @allnulled/browsie-script

Importation

In node.js:

require("@allnulled/browsie-script");

In html:

<script src="node_modules/@allnulled/browsie-script/browsie-script.js"></script>

Usage

To parse and get the AST

const ast = BrowsieScript.parse(`users?`);

Outputs:

{
  "$type": "value",
  "value": {
    "$action": "select",
    "table": "users",
    "filters": null
  },
  "appends": []
}

To parse and get the JS

const js = BrowsieScript.parse(`users?`, { toJavaScript: true });

This feature may not yet be implemented.

Syntax

It is about insert, update, delete and select. Else, we can pipe.

To insert

users+{}
users+{"name":"admin","password":"admin"}
users+[{},{},{}]

To update

users={changed:true}
users:1={name:"admin changed"}
users:"admin"={name:"admin changed"}
users:id=1={name:"admin changed"}
users:name="admin" and password="admin"={name:"admin changed"}

To delete

users-1
users-"admin"
users-id=1
users-id=1

To select

users?
users:1?
users:"admin"?
users:name="admin"?
users:name="admin" or email="admin"?
users:name="admin"|email="admin"?
users:name="admin" and email="admin"?
users:name="admin"&email="admin"?

To pipe

We have 3 types of pipe:

  • (Level 1) Modifying. Symbol: >. Used to modify the value.
  • (Level 2) Exporting. Symbol: >>. Used to export the value to local, global or wherever variable.
  • (Level 3) Returning. Symbol: >>>. Used to return from the current function.
  • (Level 4) Returning. Symbol: *. Used to multiply against functions.
users? > $.sort.by.props(_, "created_at", "name", "id")
users:(name="admin"|email="admin")&(id is not null)? > $.sort.by.props(_, "created_at", "name", "id")
users? * console.log
messages+{message:"Hello, world!"}
messages:1? * console.log