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

@siteimprove/alfa-toolchain

v0.97.0

Published

Toolchain for developing Alfa and related projects

Downloads

1,470

Readme

Alfa toolchain

This package contains the toolchain for developing Alfa and its companion projects. It is tailored-made for Alfa and makes many (poorly documented) assumptions on code structure that likely do not hold on other codebases. Therefore, it is unlikely to be re-usable by other projects.

Changelog

Alfa is using changesets. We keep one changelog per package, plus one global changelog (because we keep all packages in sync at the same version number). The per package changelogs are handled directly by changeset, using a custom generation function defined here. The global changelog is built with utilities here.

Individual changesets are expected to have the following shape (after the frontmatter):

**[kind]:** [title]

[details]

where [title] is a one line summary for the changes (the full text is called summary in changesets lingo, so we call that summary title instead), [details] is an arbitrary long detailed explanation, and [kind] is one of: Breaking, Removed, Added, Changed, Fixed`.

Breaking and Removed kinds may only be used on major bumps (or minor bumps pre-1.0.0); Added kind may only be used on minor or major bumps (and should only be used on minor bumps); Changed and Fixed kinds can be used on any bump but should only be used on patch bumps.

The individual changelog contains the full changeset. The global changelog contains only the title, with link to the individual changelog.

Validation

The package provides a bunch of low-level validation structure of the project. These checks can be toggled via ./config/validate-structure.json.

  • Check that each changeset matches the structure described above.
  • Check that each workspace has an API extractor config.
  • Check that each workspace's package.json matches the expected structure.
  • Check that each (internal) dependencies has its path referenced in the corresponding tsconfig.json.