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

hands-free-express

v2.9.1

Published

-THE ULTIMATE TOOL OF BUILDING FAST-

Downloads

7

Readme

hands-free-express

-THE ULTIMATE TOOL OF BUILDING FAST-

What was the problem?

Ah! Shit. A new project, making the folder structure, writing the same base code as other projects, copying and pasting all of them, initializing git, downloading packages, initializing package.json, running server and ... WTF BRO!?

So How Was This Solved? 🤔

Aaaa~ A good one. Well, Actually one night when I was just chatting as normal with one of my developer friends the idea came out of the cave and then I started to write it.

  • Creates Folder Structures (For both app directory and class-based(OOP) projects and functional projects (no-app)) ✅
  • Creates Some Basic and Obvious files of those directories ✅
  • Initializes package.json ✨✅
  • Installs the basic common packages (express, mongoose, morgan, cors, http-erros, http-status-codes, jsonwebtoken, dotenv and a bunch of others) 🎉✨
  • Writes the basic server code needed for both OOP and functional projects. (The require statements don't need changes ) ✨✅
  • Creates a Special response-builder names (SendResponse) ✨✨
  • Creates some very useful middlewares such as validation Error mapper and ... ✅
  • With also more utils such as a key generator for generating Secret_key for JWT tokens. ✅
  • .gitignore and git out of the box, with node_modules and .env ignored 🎉✨✅
  • Adds dev command to package.json file and runs the server for you (in functional or no-app mode)
  • What Else you want! Open an issue and let's talk!

USAGE

Downloading:

  1. Do a npm i -g hands-free-express
  2. Run the Commands ✅✨🎉

cea help helps you get along with options and things here. cea new-cb Creates a brand-new empty class-based project. cea class-based or cea cb Creates a filled and almost ready OOP based project. cea no-app Creates a Functional-suggested folder structure with the basic code you need for running your server with an index route (It's Perfect, Believe me and test it). You Don't even need to write a fucking single line of code for getting a server up and running.