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

@cran/bin.jot

v0.0.10

Published

Fast module iteration tool

Downloads

15

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

common-cranberrycommon-cranberry

Keywords

jotcranberrybin

Readme

Jot

Jot was created to provide easy iteration within the NPM ecosystem. By acting without git we can deploy faster at the cost of requiring changes to be small and independently made. There are ups and downs and the correct usage of this tool is up to your purpose.

Note from the author: For personal use I have found this tool to help drastically in micro library publications. For larger projects and any team coding exercises I still strongly recommend the use of a version control system

Installation

npm install --global @cran/bin.jot

Note: Your system may define a jot program. For this reason a jot-node command has been provided. You may either use this in place of jot or if you do not use the builtin, create an alias alias jot=jot-node somewhere in your shell configuration

Features

jot new

This will create a new project with the given name. If you do not specify a module type you will be prompted. You will also be prompted for a description and keywords for the project.

A new project will be created and configured and then behave as any other code environment. Git is provided to allow IDE integration for changes between one revision and the next.

jot edit

To edit an existing project (only if its source is stored in NPM, usually via jot) run this command, optionally with a version to cherry-pick.

After downloading the sources and moving them to the correct locations, this command behaves identically to jot new

jot clean

In case you decided to not continue working on a change, run jot clean [package-name] to remove local files.

In the event you want to ensure your system is clear of any and all jot volumes, simply run this command without providing a package name

jot publish

While this is not strictly necessary, running this command has the benefit of being prompted for what changed, allowing for automatic changelog management. This is important as we no longer have git to back the project.

This command will also clean the volume on success leaving you with a clean slate to start the next project or edit another.