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

@fhpriamo/spooky

v0.1.0

Published

SouFan's TypeScript boilerplate for Node.js libraries

Downloads

5

Readme

typescript-image jest-image npm-image

Setup

  1. Make a shallow clone of this project in the desired folder, renaming it (replace <MY_LIB_NAME> in any of the examples below for your project's name):
  • Using SSH: git clone --depth 1 [email protected]:fhpriamo/spooky.git <MY_LIB_NAME>.
  • Using HTTPS: git clone --depth 1 https://github.com/fhpriamo/spooky.git <MY_LIB_NAME>.
  1. Step into the recently cloned project and erase the .git directory completely.
  2. Make the required and optional overrides as described further below.
  3. Create a new repository with git init and commit your files.

Required overrides:

You must...

  1. update author, repository, homepage, bugs, name and version fields in package.json.
  2. delete or replace demo files: rm src/index.ts src/simple-math.ts src/__tests__/simple-math.test.ts.
  3. rewrite this README.md (after reading it);

Optional overrides:

You might want to...

  • set the license field (default is UNLICENSED). You may also include a LICENSE file on the root folder.
  • set the publishConfig.accessto public if your package is not meant to be published as a private package.
  • set the private field to false in order to publish the package.
  • set the repository field.
  • remove the test command along with the jest dependency if your project is not meant to include automated tests.
  • run yarn upgrade --latest to generate a fresh yarn.lock and upgrade all dependencies listed in your package.json.
  • exclude the .npmrc file or modify it if you're not using a SouFan NPM registry token (typically SOUFAN_NPM_TOKEN)

In addition to package.json, you might also want to check...

  • the .npmignore file for the files that will be ignored on publishing.
  • the test runner options on the jest.config.js file.
  • the linter rules in the eslintrc.yml file.
  • the general editor configuration on the .editorconfig file.