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

psdad

v0.4.0

Published

implementation of psdad data interop proposal

Downloads

8

Readme

psdad.js

NPM version

JavaScript implementation of psdad, for node.js or browsers

Example

Example (in demo.js)

const { mapper } = require('psdad')
const vocab = mapper()

class Circle { constructor (state) { Object.assign(this, state) } }
class Line   { constructor (state) { Object.assign(this, state) } }

vocab.add(Circle, 'There is a circle of radius [number radius] at position ([number x], [number y]).')
vocab.add(Line, 'There is a line from ([number x0], [number y0]) to ([number x1], [number y1]).')

const mydata =  [
  new Circle({radius: 1, x: 10, y: 20}),
  new Line({x0: 10, y0: 20, x1: 15, y1: 25}),
  new Circle({radius: 2, x: 15, y: 25}),
]

const str = vocab.stringify(mydata)
console.log(str)
/* =>
There is a circle of radius 1 at position (10, 20).

There is a line from (10, 20) to (15, 25).

There is a circle of radius 2 at position (15, 25).

*/

const mydata2 = vocab.parse(str)
console.log(mydata2)
/* =>
[ Circle { radius: 1, x: 10, y: 20 },
  Line { x0: 10, y0: 20, x1: 15, y1: 25 },
  Circle { radius: 2, x: 15, y: 25 } ]
*/

Performance

Some quick tests show stringify() running about 1m objects per second, and parse() running about about 150k objects per second. That's not as fast as the native JSON functions (maybe 50% of JSON on stringify and 10% on parse), but it's still probably fast enough. The parsing is all done with one compiled regexp. It will be interesting to see how it's affect by having larger definitions and more classes.