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 🙏

© 2026 – Pkg Stats / Ryan Hefner

citadel

v1.2.1

Published

Simple front-end boilerplate

Readme

citadel

Citadel is a very simple front-end boilerplate. It contains a set of scripts and templates to perfom operations like:

  • prepare initial project folder and file structure:
    • prepare initial HTML and SASS templates;
    • prepare initial JavaScript based on RequireJs modules.
  • prepare Grunt builder task;
  • init Git repository. The basic idea of Citadel scripts set is a fast project initialization with pre-defined production build flow. By default Citadel requires you to organize your project in appropriate way - use RequireJS, SASS. As a result you production version would use only one minified JavaScript file (besides the require.js file itself) and only one CSS file.

CD to your project folder and simply run command citadel. It copies template files, downloads node modules for Grunt build task and initializes Git repository inside the current folder.

Citadel boilerplate has the following folder structure:

  • dev - contains the developer version of your project:
    • sass - contains main SASS-template file and predefined mixins;
      • main.scss - main SASS-template file for Citadel project;
      • _base.scss - contains initial SCSS rules to import;
      • _mixin.scss - contains pre-defined SCSS mixins to import.
    • css - folder for your CSS-files, main SASS-template file will be compiled inside this folder;
    • images - folder for your image files;
    • fonts - folder with fonts;
    • js - folder for your JavaScript:
      • app.js - the main JavaScript file for Citadel project;
      • require.config.js - requirejs config for Citadel project;
      • vendor - folder for JavaScript libraries like jQuery and RequireJS.
  • prod - folder for the production version for Citadel project.
  • index.html - main HTML file for Citadel project.
  • .gitignore - list of files for GIT to ignore by default.
  • package.json - config with dependencies Citadel project use by default.
  • Gruntfile.js - default Grunt builder config.
  • run.sh - launcher for developer SASS watcher.

##Gruntfile.js Running grunt command inside the Citadel project directory will execute the Grunt builder task. Builder executes the following operations:

  • compile and minify your app.js file into app.min.js;
  • compile scss/main.scss into css/main.css;
  • clean production directory;
  • copy project files to production directory, by default the following tasks will be done:
    • copy images and fonts folders as is into prod directory;
    • copy css/main.css into prod directory;
    • copy index.html file into prod directory, during this copy process the require.config.js will be removed from the html code. All additional html files must be configured to copy manually in Gruntfile.js.
    • copy js/app.min.js into prod directory as app.js;
    • copy require.js into prod directory;