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

@crazyfactory/tinka

v1.9.3

Published

A dependency-free library to gracefully handle fetch requests.

Downloads

537

Readme

tinka

npm Build Status codecov dependencies Status devDependencies Status semantic-release Greenkeeper badge npm version

A dependency-free library to gracefully handle fetch requests.

Usage

Tinka can be used as a standalone requirement or better yet as a basis for fully typed API SDKs.

Contribute

Clone this repository and install project dependencies.

  • npm install

Tests

This package is tested using jest, which you can use via CLI or through most IDEs directly.

  • on CLI execute npm test to run the tests.

This will also create a code coverage report at /coverage.

For continuous testing use wallabyjs with our default configuration at ./wallaby.js

Code styles

This project uses tslint to enforce similar code styles across source and test files. Passing tslint validation is a CI requirement. You can run and validate your code style locally.

  • npm run lint lints all typescript files in the project.
  • npm run lint-fix to also fix most common errors automatically.

The project also comes with project based code-style settings for intelliJ-based IDEs like PhpStorm, Webstorm etc. You can safely use their auto cleanup features.

Build and deploy

This package is automatically build and deployed using TravisCI and semantic-release. You can however test the process locally:

  • npm run build compile sources into all desired formats.
  • npm run pack to create the final package.

Note: You'll have to edit package.json to include a version number of your choice. Don't check this in though as the version number is determined by semantic-release.