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

ez-compiler

v1.0.0

Published

An easy-to-use compiler and creator for commonly used pre-processors.

Downloads

8

Readme

EZ-Compiler

A fast and easy tool to get your project up and going, then watch it, and build it!

How to install:

npm install -g ez-compiler

How to get started with a project:

  1. npm init or npm init -y (If you're lazy like me and want npm to answer all the questions for you)
  2. ezc create default OR ezc create angular1 (with any flags you like. See listed below.) Files will be created in a ./src directory. The file structures for default and angular1 are shown below
  3. npm install to install the preprocessor flags you added
  4. ezc compile (to watch and automatically compile and build files) Once the files are compiled, they will automatically be put into the ./dist folder.

!!!!Please don't change the directory names. This tool will not work if you change "src" or "dist"!!!!

Flags for "create":

When you run ezc create default OR ezc create angular1, you can add flags to use preprocessors, like SASS, Pug/Jade, Coffeescript, and more. These change the file extensions in the src directory to the corresponding file extensions. These are the current flags that exist as of right now. Please don't hesitate to suggest ones that should be added. NOTE: When flags are added, the file extensions for files related to that preprocessor will be changed. i.e. .css -> .sass

  • --stylus for Stylus
  • --sass for Sass
  • --scss for Scss
  • --pug for Pug/Jade
  • --coffee for Coffeescript
  • --babel for Babel

File Structures:

Default