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

@ryanflorence/testing-123

v0.0.3

Published

The simplest typescript package template I can think of.

Downloads

119

Readme

package-name

The simplest typescript package template I can think of.

  • Node built-in testing: node:test and node:assert
  • TypeScript with Node's --experimental-strip-types instead of compiling
  • Develop, test, debug directly in your code with VSCode's built-in features, no CLI + console.log shenanigans
  • Publish with npm version and a GitHub action

Setting up

  1. Install Node Test Runner Extension
  2. Click the "Testing" tab in the VSCode Activity Bar
  3. Reload VSCode Window or restart vscode if you don't see any tests in the sidebar

Development

  1. Open a test file
  2. Click the testing buttons in the gutter to run a test
  3. Set breakpoints in the gutter and run the test in the debugger (click the play button in the error popup with the bug on it)

Keyboard shortcuts

  • Run all tests in the current file with Command + ; + f
  • Run current test at the cursor with Command + ; + c

Playing around

You can run any file in the debugger with F5. Or click the debug icon in the Activity Bar and click the play button up top.

CI Scripts

# run tests
pnpm test
# compile typescript to ./dist
pnpm build

Releasing

Setup

First add an NPM token to your GitHub repository secrets. Log into npm to get one.

Publishing a Release

Create a tag and update package.json with npm version

# npm version patch | minor | major
npm version patch

Then push to GitHub.

git push origin main --tags

The GitHub action will match the tag and release.