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

balena-typescript-skeleton

v2.2.0

Published

Skeleton template for a balena TypeScript project

Downloads

23

Readme

Skeleton Project

This is a skeleton template for a TypeScript library project, containing all the default files and settings required for a balena project. As a result package-lock files are disabled so that upstream dependency issues are surfaces on our CI. In case that you are implementing a standalone project, you can enable them by deleting the .npmrc.

Modify the package.json, and README.md file as required, npm install, then implement code in the lib directory.

Compiled code will be output into the build directory (transpiled JS, declaration files and source maps).

npm test will run the tests on both node and a browser. In case that you are implementing a node only library, you can just just drop karma.conf.js and all karma related references in the package.json.

Integrating with balenaCI

After cloning & scaffolding the repository

  • Reset the package.json version to the desired one for the initial release, eg 0.1.0.
  • Delete the CHANGELOG.md & .versionbot folder.
  • Set the appropriate .github/CODEOWNERS.
  • Push the scaffolded project to master
  • Create a new branch and open a PR for it.
  • After balenaCI picks up the PR, go to the repository's settings page and add a master branch protection rule and mark the balenaCI checks as required.