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

frontpack

v1.0.2

Published

A starter build framework.

Downloads

33

Readme

Frontpack GitHub version

Code Climate Build Status dependencies Status devDependencies Status Join the chat at https://gitter.im/frontpackbuild/Lobby Gratipay User Beerpay

Build next generation, standards-driven, optimized websites & applications with Frontpack. Get a jumpstart on development with Foundation, React, Babel & more!

Why Frontpack?

Prerequisites

Direct Download

Download the script here and include it (unless you are packaging scripts somehow else).

Installation

Navigate to the frontpack directory in Terminal and run the following commands:

  1. $ npm install To install dependencies
  2. $ npm start Build & watch files

Development Usage

The following node commands are available:

  • $ npm start (or npm start) Starts the project in the development mode. Surf to localhost:8080 in your browser to see it running.
  • $ npm run build Generates a production build below build. You can open the generated index.html through the browser to examine the result.
  • $ npm run lint:js Executes ESLint against the code. ESLint is able to catch smaller issues. The default setup lints even during development so you rarely need to execute this command yourself.
  • $ npm run stats Generates statistics (stats.json) about the project. You can analyze the build output further.
  • $ npm run styleguide Generates a style guide. The default setup generates one even during development so you rarely need to execute this command yourself.
  • $ npm run deploy Deploys the project to GitHub pages.

Removing Unused CSS

The default setup removes unused CSS during production builds using PurityCSS by scanning all files in the purifyOptions.paths setting in the webpack configuration file. Unfortunately, due to how webpack handles files in memory, PurityCSS is unable to scan URLs. To solve this, Frontpack allows you to run uncss outside of webpack by running the following:

$npm run --silent uncss [url(s)] > dist/css/[filename].css

Replace [url(s)] with the URL(s) uncss should scan and [filename] with the name of the output file. (ex. npm run --silent uncss https://bmarshall511.github.io/frontpack/ > dist/css/global.bundle.css).

IMPORTANT: For production builds using uncss, npm run build should be run first, then the uncss command above to ensure the file stays minimized. Also, be sure not to leave out the --silent argument or the node command will be added to the top of the outputted file. To change uncss options, use the .uncssrc file.

Contributing

Check out the Contributing Guidelines.

Security

For vulnerability reports, send an e-mail to me at benmarshall dot me.

Authors

Changelog

v1.0.2 (Oct. 12, 2017)

  • Fix for bugs url in node package.
  • Fix for false positive errors when using the rem-calc (https://github.com/bmarshall511/frontpack/issues/3)
  • Update to the output path for the webpack loadFonts part (https://github.com/bmarshall511/frontpack/issues/7)
  • Update to stylelint's output warnings (https://github.com/bmarshall511/frontpack/issues/4)
  • Update to the selector-class-pattern to comply with BEM (https://github.com/bmarshall511/frontpack/issues/2)
  • Added gh-pages
  • Added a custom variables sass file (https://github.com/bmarshall511/frontpack/issues/6)
  • Added uncss as an option to remove unused CSS

v1.0.1 (Oct. 10, 2017)

  • First public release.