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

maverick-cli

v1.4.0

Published

A simple CLI for scaffolding my projects.

Downloads

4

Readme

Maverick CLI lets you create a scaffolding for your next project with ease. Maverick CLI is based on a popular Yeoman generator webapp, with some changes.

Features

  • enable ES2015 features using Babel
  • CSS Autoprefixing
  • Built-in preview server with BrowserSync
  • Automagically compile Sass with libsass
  • Automagically compile Pug
  • Automagically lint your scripts
  • Map compiled CSS to source stylesheets with source maps
  • Awesome image optimization
  • Automagically wire-up dependencies installed with Bower

Installation

On macOS, Linux, or Windows run the following:

npm install -g maverick-cli

That is it!

Gulp Commands

  • gulp serve to preview and watch for live changes
  • gulp or gulp build to build the app for production
  • gulp serve:dist to preview the production build

CLI Commands

Init

maverick init <path> [Project name] [options] - to scaffold your webapp ( is optional)

Options:

--skip-install to skip the execution of bower and npm installation after scaffolding.

SASS

maverick sass [options] [File name] - create a SCSS file.

Options:

Options argument is required.

  • -c or --component to add a component, this also adds a css selector.
  • -e or --element to add an element
  • -t or --tool to add a tool
  • -u or --utility to add a utility
  • -p or --plugin to add a plugin

Example

maverick sass -c "responsive-img"

Pug

maverick pug [File name] to create a pug page

Options:

  • -t or --title <title> to add a title to the page

If you don't provide the title it will be empty.

Project Structure

There is a well-defined project structure that must be respected.

src
├───fonts
├───images
├───js
├───sass
│   ├───components
│   ├───elements
│   ├───generic
│   ├───plugins
│   ├───tools
│   └───utilities
└───views
    ├───inc
    └───layouts

SASS Folder

This is where all the .scss files are found, gulp will watch for changes in this folder.

  • /components - Complete chunks of UI, like navigation, cards, panels etc..
  • /elements - Unclassed HTML elements, like a, h1, body, blockquote etc..
  • /generic - Reset and normalize css.
  • /plugins - SCSS files from imported plugins, like owl-carousel, popper etc..
  • /tools - Mixins and functions
  • /utilities - Override and helper functions, they are usually high-priority (!important)

SCSS files shouldn't be created manually, CLI should be used for that.

Views folder

This is where all the .pug files are found, gulp will watch for changes in this folder.

  • inc - Page parts that are included in a template, like header, footer, navigation etc...
  • layouts- Templates that are extended by the pages.

In the root of the views is where the pages are located.

Notes:

If the project hasn't been generated by Maverick CLI commands (scss, pug) won't work.