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

macropod-tools

v0.0.29

Published

Development server and build tools for webpack and React, used by Macropod's products.

Downloads

41

Readme

Macropod Tools

Development server and build tools for webpack and React, used by Macropod's products.

What's the problem?

Keeping the webpack configuration and build processes in line between our products has been tricky.

We've run into confusing issues which ultimately stemmed from the slightly different configurations being used in Stack, Macropod Components and Brief.

We anticipate this getting more complex as we introduce more tooling, for things like tests.

What does it do?

This collection of configuration files and utility programs provide two things:

  1. One baseline configuration for webpack across all our products.
  2. Identical processes for making production builds, running tests, and running development servers.

How do I use it in my project?

If you're starting a new project, things are a bit involved. See this issue for progress on this part of the documentation.

We currently have this built into Stack, Brief and Macropod Components.

If there's some specific tooling which is confined to a single project, or worse, duplicated across several, feel free to log an issue on this project so it can be moved here and maintained in one place.