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

create-sock-project

v1.0.2

Published

A Node CLI used to generate the config files and boilerplate code I often use.

Downloads

3

Readme

create-sock-project

Usage

yarn global add create-sock-project
create-sock-project

Roadmap

  • [x] Prompt user for technology, write config files in current working directory
  • [x] Generate package.json and install necessary dev dependencies for config files (eslint, prettier, etc.)
  • [ ] Display yarn's log (progress bar and dependencies)
  • [ ] Refactor write config files functions. Currently not DRY.
  • [ ] Create default boilerplate code for express, react, and next
  • [ ] Generate and write default boilerplate code to cwd for each framework
  • [ ] allow directory to be passed as an argument, default to current working directory (ex: npx create-sock-project ., npx create-sock-project my-first-project)
  • [ ] install all dependencies once files have been copied
  • [ ] create multiple boilerplate options for each specific framework (database type for express, rest or graphql, routing, authentication, etc.)
  • [ ] Ask user for specifics on what they want to use for each framework (database type, routing, authentication, etc.)
  • [ ] generate and write files for project per these specifications