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

web-frontend-boilerplate

v1.2.2

Published

A boilerplate for developing frontend UI application

Downloads

22

Readme

my-frontend-boilerplate

travis build version downloads WTFPL License

My interpretation of how a boilerplate with a minimum set of tools should look like for my frontend application development. :bowtie::pray:

Screenshot

Why?

Because I start to keep repeating over and over again scaffolding my project structure, especially when constructing my favorite webpack.config.js and package.json files.

Note that the webpack configuration should be easily extensible to pack popular modern JS frameworks. It might as well be flexible to switch from the webpack-dev-server to more customized Node.js Express server, which uses the webpack-dev-middleware.

Molly's automation principle:

Do it once, just do it. Do it twice, take notes. Do it three times, automate. :raising_hand:

What's on the Stack

  • JavaScript ES6+ (Babel).
  • Bootstrap 4 (and Font Awesome).
  • lodash.
  • jQuery.
  • webpack 4 (and its development server).

Installation

  • Install Node.js LTS and npm from its website, or better even, use nvm.

  • Install yarn.

  • Checkout the repo, cd to project directory, and setup dependencies:

$ yarn install:clean
  • For development, start webpack development server with hot reloading capability:
$ yarn start

You'll find the app running on https://localhost:8080.

  • For production, build frontend static assets:
$ yarn build

Then, simply drop all files under assets directory to the production server.

Author

Glenn Dwiyatcita (@dwiyatci)

License

WTFPL – Do What the Fuck You Want to Public License.

See LICENSE.txt.

WTFPL