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

@juststarting00/minimal-ts-library

v1.1.0

Published

A minimal TypeScript library that uses NPM. See README for further info

Downloads

1

Readme

Minimal TypeScript Library

This is a template for a TypeScript library that has the following already properly set up:

  • Library can be consumed in NPM
  • Library can be consumed in an HTML file (load using <script> tag)
  • A development JS file that has source maps that points back to the TypeScript files for debugging
  • A production JS file that is minified / uglified
  • Library exposes more than 1 class

This library is an algorithmic library - meaning it's not doing any HTML UI work, just straight algorithmic-like code using JavaScript.

Other things that got accomplished:

  • Definition files got generated
  • Learned about re-exporting: https://www.typescriptlang.org/docs/handbook/modules.html

It has been a rather frustrating learning experience (for me) to get this far. Links that helped to produce this:

  • https://marcobotto.com/blog/compiling-and-bundling-typescript-libraries-with-webpack/

    Suggested creating CommonJS build, ES6 build and a UMD build. However, uses old Webpack v2 and the webpack.config.js isn't valid anymore

  • https://derekworthen.com/posts/authoring-typescript-libraries/

    Suggested also outputting d.ts files. However, the article uses babel which is no longer needed in newer Webpack

  • https://webpack.js.org/guides/typescript/

    The prior 2 articles' webpack.config.js didn't quite work, so I ended up using the config on webpack's website. Source map config is also from this article

  • https://webpack.js.org/guides/production/

    This article suggests using different config files

  • https://stackoverflow.com/questions/64639839/typescript-webpack-library-generates-referenceerror-self-is-not-defined

    Prior configs result in library not usable in NPM environment