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

incremental-game-lib

v0.0.1

Published

A library to help build incremental games.

Downloads

2

Readme

Typescript lib starter

Build Status Standard Version

based on https://github.com/elboman/typescript-lib-example and http://marcobotto.com/compiling-and-bundling-typescript-libraries-with-webpack/

  • proper package.json file references for build
  • compiles esm-lib to vanilla es2015 instead just es2015 modules
  • compiles types to typings folder instead of multiple distribution
  • umd is shiped under umd folder instead of _bundles

Consumption of published library:

library is shiped in 3 formats:

  • raw es2015 module and code format ( ideal for tree shaking with Webpack 2 )
  • CommonJS format for bundler consumption
  • UMD format for usage withou bundler

Webpack

// main.ts
import {Greeter} from 'my-lib';

const mountPoint = document.getElementById('app');
const App = () => {
  const greeter = new Greeter('Stranger');
  return `<h1>${greeter.greet()}</h1>`
}
const render = (Root: Function, where: HTMLElement) => {
  where.innerHTML = Root();
}

render(App, mountPoint);
<html>
  <head>
    <script src="bundle.js" async></script>
  </head>
  <body>
    <div id="app"></div>
  </body>
</html>

UMD ( no bundler )

<html>
  <head>
    <script src="node_modules/my-lib/umd/my-lib.min.js"></script>
    <script async>
        var Greeter = MyLib.Greeter;

        var App = function() {
          var greeter = new Greeter('Stranger');
          return '<h1>'+greeter.greet()+'</h1>'
        }
        var render = function(Root, where) {
          where.innerHTML = Root();
        }

        render(App, mountPoint);
    </script>
  </head>
  <body>
    <div id="app"></div>
  </body>
</html>

Release

yarn release

Initial Release (without bumping package.json version):

yarn release -- --first-release

Check what files gonna be published to npm

  • CLI output via yarn release:preflight
  • or yarn release:preflight:package will create tarball which you can check

Check size of your published NPM bundle

run yarn build then npm run size

Format and fix lint errors

yarn ts:style:fix

Commit ( via commitizen )

yarn commit