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 🙏

© 2024 – Pkg Stats / Ryan Hefner

sexpr-plus

v7.0.0

Published

S-expression parser, with quoting and comments

Downloads

99

Readme

sexpr-plus npm package CI status

Recursive descent parser for S-expressions, with features useful for writing an S-expr-based programming language. Written for eslisp, but generalisable.

Outputs an array containing objects representing parsed forms:

  • Lists are parsed to { type: "list", content: [ <other objects>... ] }.
  • Atoms are parsed to { type: "atom", content: "<atomName>" }.
  • Strings (delimited with "s) are parsed to { type: "string", content: "<atomName>" }. They support the same escape sequences as JavaScript strings: \", \\, \n, \r, \t, \f, and \b.
  • Supports quote, quasiquote, unquote and unquote-splicing, with ', `, , and ,@. They're turned into the appropriate atoms.
  • Comments are from ; til end of line. They are not present in the output.

Empty inputs or inputs containing only comments produce an empty array.

Forked from the more minimal fwg/s-expression.

Node locations

All output nodes also have a location property, showing where in the input that node originated:

{
    start : { offset, line, column },
    end : { offset, line, column }
}

All are integers: offset is the number of characters since the input, line and column are 1-based and self-explanatory.

These may be handy for constructing source maps or showing more detailed error messages.

Usage

npm i sexpr-plus
var parse = require("sexpr-plus").parse;

Call parse with a string containing code to parse.

If you need to catch and distinguish between different types of Error with instanceof while parsing, the syntax error prototype is available at require("sexpr-plus").SyntaxError.

License

MIT.