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

ts-boilerplate

v1.0.1

Published

TypeScript boilerplate for React library development

Downloads

2

Readme

ts-boilerplate

TypeScript boilerplate for React library development

Uses:

  • karma
  • react
  • rollup
  • tslint

See ts-test-boilerplate for a test app that consumes this library.

Files to edit after cloning

* dist/bundle.d.ts
* package.json
* rollup.js
* src/**/*.ts
* test/**/*.spec.ts

Things to note

Since the main bundle is separate from the test bundle, it's easy to accidentally publish an outdated package. Use npm run pub to ensure your main bundle is up to date before publishing it.

Objectives

  • Minimize duplication of config (e.g. I wrote a customized rollup script instead of using the usual rollup.config.js so I can combine options for both the main & test builds)
  • Minimize reliance on packages that aren't well maintained (e.g. at the time I tried the rollup-plugin-typescript package, I wasn't getting TypeScript compilation error messages).
  • Small, quick and easy to understand bundle output (which rollup fulfils rather nicely)

Lessons learnt

  • Using TypeScript for build scripts (e.g. rollup.js used to be rollup.ts) led to significant pain. tsc can compile to either CommonJS or ES2015, but rollup wants ES2015 whereas node.js scripts wants CommonJS (i.e. require statements). Addressing this discrepancy made the config files & build scripts unnecessarily complex and error-prone, so I just went back to *.js files.