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

@aurelien.lair/typescript-tdd

v1.0.8

Published

## Description

Downloads

1

Readme

TypeScript learning in TDD

Description

This project has as scope an experimental learning of TypeScript in TDD with Jest framework

Getting Started

The following instructions will allow you to set the project up from scratch.

System requirements

Nodejs

This project needs NPM scripts and NodeJs installed on your local machine.

Commands

Command-line interface

To install the dependencies

npm install

To run the test suite

npm test

NPM Package publish

You can publish the current package on the NPM registry. To do this you need to configure on your account a proper access token then run

cp {.env.dist,.env}

At this point you should have a proper .env file you just need to add your token instead of THIS_IS_A_SUPER_SECRET

NPM_TOKEN=THIS_IS_A_SUPER_SECRET

Assuming you have generated a new semantic release version of the package (ie. the version in the package.json has been changed) you can now publish it, first try in a dry run mode

source scripts/setenv.sh && npm publish --access=public --dry-run

Then publish it

source scripts/setenv.sh && npm publish --access=public

Git commit message convention

This projects follows the conventional commits.

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Example:

docs: add description of TypeScript run command

| Type | Description | |------| ----------- | | style | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) | | build | Changes to the build process | | chore | Changes to the build process or auxiliary tools and libraries such as documentation generation | | docs | Documentation updates | | feat | New features | | fix | Bug fixes | | refactor | Code refactoring | | test | Adding missing tests | | perf | A code change that improves performance |