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

jjsync

v0.1.11-1

Published

watches two files, a json and a js, ( defaults are ```package.json``` and ```package.jsos``` ) and makes them sync'ed

Downloads

2

Readme

jjsync

Synchronizes package.json and package.js

jjsync watches two files ( defaults are package.json and package.jsos ) and makes them sync'ed

Example

You just edited your package.jsos and commented task3:

{
  name : "jjsync",
  scripts : {
    task1 : "echo task1",
    task2 : "echo task2",
    //task3 : "echo task3"
  }
}

after saving package.json syncs:

{
  "name" : "jjsync",
  "scripts" : {
    "task1" : "echo task1",
    "task2" : "echo task2"
  }
}

then you install lodash library

yarn add lodash

after installation, package.json gets altered

{
  "name" : "jjsync",
  "scripts" : {
    "task1" : "echo task1",
    "task2" : "echo task2"
  },
  "dependencies" : {
    "lodash" : "^4.17.21"
  }
}

then package.jsos gets sync'ed

{
  name : "jjsync",
  scripts : {
    task1 : "echo task1",
    task2 : "echo task2",
    //task3 : "echo task3"
  },
  dependencies : {
    lodash : "^4.17.21"
  }
}

Usage

cd your-project
## defaults are json=package.json and js=package.jsos
npx jjsync [ json=json-file ] [ js=js-file ]

Considerations

js-file is created if it doesn't exist.

Comments are ignored outside of the main object {}

Because of beta status, ie if something may fail, every time a synchronization occurs, a file ( .package.json_history ) gets appended with the latest package.json content.