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

@jkuebart/parseq

v20201109.0.0

Published

Douglas Crockford's parseq, packaged for Node.js.

Downloads

30

Readme

Douglas Crockford's parseq

This package provides Douglas Crockford's public-domain parseq library as a Node.js package. The package version indicates the upstream »edition«.

Both a universal CommonJS/AMD module and an ECMAScript 6 module are provided.

Notable features of this package are:

  • its major version number is equal to the parseq »edition«
  • it is automatically updated when a new edition of parseq is released
  • it contains unaltered parseq source code
  • the code is JSLint-clean

Versioning

The major version number of this package indicates the parseq »edition« it contains. Multiple updates to parseq on a single day are represented by increasing minor version numbers. The patch version indicates updates to this package itself.

Usage from Node.js

This package can be installed using

$ npm install @jkuebart/parseq

For more detailed examples, see the website.

const parseq = require("@jkuebart/parseq");

parseq.sequence(
    requestor_array,
    time_limit
)

Usage from HTML

This is the easiest way to include parseq into a website:

<script type="module">
    import parseq from "//unpkg.com/@jkuebart/parseq/dist/parseq.min.js";

    // …
</script>

If you're having to support browsers which can't handle ES6 modules, you can simply load the universal module which provides a global variable parseq:

<script src="//unpkg.com/@jkuebart/parseq/dist/parseq.umd.min.js"></script>

Alternatively, CommonJS and AMD compatible loaders can also load the universal module.

Updating

A shell script is provided for building new packages when this project or the upstream project is updated. It can be run using

npm run editions

This creates branches and tags based on the »edition« of the upstream project. Packages still need to be generated and published manually.

The local branches and tags can be viewed using

npm run show-branches
npm run show-tags

This can be used to automate some tasks, for example:

npm run show-branches --silent |
while read b
do
    git push --set-upstream origin "${b#refs/heads/}:${b#refs/heads/}"
done

or

npm run show-tags --silent |
while read t
do
    git checkout "${t#refs/tags/}"
    npm publish --access public
done

To easily remove automatically created local branches and tags, use

npm run reset

There is also a shell script that determines whether the upstream project has new commits.

npm run show-branches --silent |
npm run uptodate --silent