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

@0x4447/tomato

v1.18.18

Published

πŸ… Our personal default template for a ExpressJS projects

Downloads

116

Readme

πŸ… Tomato

Tomato is our take on the express-generator CLI that comes with ExpressJS. We created the project because we were spending too much time on bringing the default ExpressJS template up to speed, especially when we had to constantly spin up new micro-services.

One nice feature of this project is that it's simple for you to customize. If you have your own style, just clone this repo and edit the source folder to suit your needs.

How to install

] sudo npm install -g @0x4447/tomato

How to use

] tomato -d PATH_TO_FOLDER

Where to get help

] tomato -h

What to expect

There are two templates in the source folder, one for building a Website in ExpressJS, and another for building an API. In this case, the API template is a stripped-down version of the Website folder - with some minor changes. Below you'll find the list of all the shared features, but not limited to features they don't share in common.

Shared key features

  • Our preferred personal commenting style
  • A simplified and thoroughly explained server file that immediately demonstrates what each line of code does
  • Clustering used by default
  • Redesigned handling and display of errors
  • Knex used by default to talk with the database
  • Code to start the server in workers folder since it's a worker and we always end up with more than the server
  • Everything organized in the way we like it :)

Website

  • Redirect to HTTPS in production
  • Compression used by default when sending requests
  • Hogan used by default for templating (nice and simple)
  • Favicon done right: Make five icons with Real Favicon Generator
  • Basic Open Graph support
  • Twitter Cards support

API

  • Throws error if there is no HTTPS in production
  • Removes the ETag from the header response
  • Removes the Data entry in the header response
  • Built-in check for an API Key

The entire flow to get the project up and running follows:

] sudo npm -g install @0x4447/tomato

Once you have this npm package installed globally, you can use it anywhere. Go to a folder in which you'd like to create a new project, then:

] tomato -d PATH_TO_FOLDER

Select the option that best suits your needs, then go into the directory you just created and type:

] npm install

Next, create a .env file to load your environment variables into memory - thanks to foreman. Or you can install another of our tool, env-auto in this manner:

] npm install cucumber -g

In your project's root folder, type:

] cucumber -s PATH_TO_FOLDER

This automatically creates the .env file created from the app.json file. The last step is to start the whole thing with:

] npm start

WARNING

This tool will override, destroy, kill, and crash everything in its path. You've been warned! ;)

Fork it

We designed this project in such a simple way that you can make it your own. Once forked, just change the content of the source folder, and you'll have your own easy-to-use template up and running whenever you need it.

The End

If you enjoyed this project, please consider giving it a 🌟. And check out our 0x4447 GitHub account, which contains additional resources you might find useful or interesting.

Sponsor 🎊

This project is brought to you by 0x4447 LLC, a software company specializing in building custom solutions on top of AWS. Follow this link to learn more: https://0x4447.com. Alternatively, send an email to [email protected].