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

vitalizer

v8.4.0

Published

Vital Software front-end asset builder

Downloads

234

Readme

Vitalizer Build status npm version

Webpack development and bundling tool for Vital Software.

Features

  • Hot reloading
  • Injected JS/CSS assets
  • Tree-shaking optimization
  • Cache busted production assets
  • Source map support
  • PostCSS (Autoprefixer, SCSS style syntax)
  • CSS Module support
  • cssnano minification
  • rem() function support

Contributing

All changes that are pushed to the master branch are deployed via a Buildkite pipeline. The pipeline runs tests, builds a Docker image, builds the release artifacts for NPM, and the library itself to an NPM registry. Use the Commit Message as documented in our Contributing Guide to trigger a release.

Installing

To install, run the following commands:

yarn add vitalizer -D

Usage

Development

To run Vitalizer in development mode (using webpack-serve), run the following command:

vitalizer start

To build your project files for production, run the following command:

vitalizer build

Configuration

To configure Vitalizer, create a file called .vitalizer in the root of your project:

VARIABLE=name

And set any of the following variables:

| Variable | Development | Production | Usage | | :---------------- | :--------------------- | :----------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CDN_URL | :x: | :white_check_mark: | When set, production assets are output as [CDN_URL][asset] rather than [asset]. Used to support an external CDN for assets. | | CI | :large_orange_diamond: | :white_check_mark: | When set to true, Vitalizer treats warnings as failures in the build. Most CIs set this flag by default. | | DISABLE_HASH. | :x: | :white_check_mark: | When set to true, production assets are output as [name].[ext] rather than [name][hash].[ext]. Useful for debugging and test purposes. | | HOST | :white_check_mark: | :x: | By default, the development web server binds to localhost. You may use this variable to specify a different host. | | INDEX_FILES | :white_check_mark: | :white_check_mark: | Comma seperated list of HTML files to use. Defaults to static/index.html. | | PORT | :white_check_mark: | :x: | By default, the development web server will attempt to listen on port 3000 or prompt you to attempt the next available port. You may use this variable to specify a different port. | | RESOLVE_MODULES | :white_check_mark: | :white_check_mark: | Comma seperated list of module roots to use other than node_modules. i.e. app, static |

Expanding Environment Variables In .env

Expand variables already on your machine for use in your .env file (using dotenv-expand).

For example, to use the DOMAIN variable:

DOMAIN=www.example.com
FOO=$DOMAIN/foo
BAR=$DOMAIN/bar