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

@jakzo/project

v0.0.3

Published

Javascript project tooling in a box.

Downloads

1

Readme

@jakzo/project

Javascript project tooling in a box.

Usage

Run yarn init to create a blank project (no .gitignore file, no tooling installed, just a package.json) then run:

yarn add -D @jakzo/project

That's it! All the tooling should now be set up. Note that you may need to restart your IDE for the integrations to pick up the changes.

Why use this instead of Yeoman or even just copying a boilerplate folder?

For free maintainence. This package is more than just a template for code; all the tooling and configuration is inside a dependency which means that by running yarn upgrade @jakzo/project --latest your tooling will be updated to the current state-of-the-art JS project setup. Any bugs in tooling can be fixed and tool dependency versions upgraded. These upgrades can even be automated with a bot like Renovate. With templates they help you get started quickly but leave all the maintenance to you. If you have many separate repositories, the maintenance time savings add up quickly.

Why would I not want to use this?

If you require a unique tooling setup which the project's setup is not compatible with or you don't like my choice of tooling. Right now it only caters for a narrow set of projects but in the future I'd like to see it be made modular where you can create extensions which add new technologies and associated linting rules. You can always start off with it then eject when you need.

How do I eject?

That's a manual process for now. The basic idea is to remove the dependency and add in all the tooling yourself. One way you could do this is by installing all the packages depended on by @jakzo/project, replacing all the config files with the config that they retrieve from node_modules/@jakzo/project, then run yarn remove @jakzo/project.