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

mimosa-vulcanize

v0.1.0

Published

A module that integrates Polymer's vulcanize with Mimosa's build workflow

Downloads

5

Readme

mimosa-vulcanize

Overview

This module uses Polymer's vulcanize build tool to concatenate web components into a single file during Mimosa's optimization process.

For more information regarding Mimosa, see http://mimosa.io.

Usage

Add 'vulcanize' to the list of modules in your project's mimosa-config.js file. That's all! Mimosa will install the module for you when you start mimosa watch or mimosa build.

Functionality

This module will run vulcanize as part of Mimosa's optimized build (mimosa watch -o or mimosa build -o).

By default, mimosa-vulcanize looks for a file named components.html at the top level of your app's source directory (watch.sourceDir). It then passes that file to vulcanize, which takes care of replacing all HTML imports with the contents of the referenced web components. The result of this vulcanization process is written to a file of the same name, components.html, within the app's compiled directory (watch.compiledDir).

For details on how vulcanize works, check out the project's documentation.

Default Config

vulcanize: {
  filename: 'components.html',
  strip: true,
  inline: true,
  csp: true
}
  • filename: The name of the HTML file to feed to vulcanize, relative to watch.sourceDir.
  • strip: If true, all whitespace and comments will be removed from the vulcanized file.
  • inline: If true, all web component assets (scripts and css) will be inlined in the vulcanized file.
  • csp: Whether to extract all inline scripts to a separate file of the same name (components.js). If both inline and csp are enabled, all javascript (inline and external) will be pulled into a separate JS file, leaving only markup and style inside components.html.