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-3h-app

v0.5.0

Published

A simple app initializer.

Downloads

5

Readme

create-3h-app

A simple app initializer.

Introduction

This is a CLI tool that helps you quickly initialize a development environment for your awesome front-end app.

Usage

$ create-3h-app --help
A simple app initializer.

Usage:
  create-3h-app [options]

Options:
  --name, -n <pkg>              The name of the package
  --author, -a <name>           The author of the package
  --desc, -d <description>      The description of the package
  --keywords, -k <words...>     The keywords of the package
  --repo, -r <repository>       The repository of the package
  --no-install                  Do not install dependencies instantly
  --help, -h                    Show help info

Example

npm init 3h-app -- -n my-awesome-app -a Peter -d "This is my awesome app".
# or
npx create-3h-app -n my-awesome-app -a Peter -d "This is my awesome app".

Template Structure

my-awesome-app/
+-- public/
| +-- index.html
| `-- index.css
+-- src/
| `-- index.js
+-- test/
| `-- index.html
+-- .gitignore
+-- LICENSE
+-- README.md
+-- rollup.config.js
`-- dev-server.js

Workflow

Generally, you

  1. Write your source code in the src folder;
  2. Test your app using the dev server (by executing npm test) which loads your source code directly;
  3. Build your app by executing npm run build;
  4. Deploy your app in the public directory...

Built-in Scripts

| name | description | |:--------|:-----------------------| | test | Launch the dev server. | | build | Build your code. |

The development server employs herver to serve your app for testing. It will serve your source code directly from src so that after you change something in your source code, you just need to refresh your page to test it. Other resource files are supposed to be put in the public folder, and they will be served properly by the development server. Additionally, files of local libs inside /node_modules can be loaded using URLs starting with /node_modules.

After building your code by executing npm run build, a bundled JavaScript file(index.js) will be placed in the public folder, which will be transformed by babel, bundled by rollup and minified by terser. Finally, you should get your app in the public folder.

License

MIT License.