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

polymer-micro-build-toolbox

v1.0.1

Published

a module mixing HtmlSplitter, getOptimizeStreams, and the polymer-build library as custom build helpers

Downloads

14

Readme

polymer-micro-build-toolbox

This package provides polymer-build module and the getOptimizeStreams helper from the polymer-cli project. It also provides the merge-stream for merging sources and dependencies during the building process, gulp-filter to remove the index.html file from the processed sources (see the example). The reason I gathered these tools is because I don't directly use the polymer CLI and needed a way to minify and bundle my application shells.

install

You can use yarn to install this package

yarn add polymer-micro-build-toolbox --dev

example

Here's one example using this module to customize your polymer build workflow

const {PolymerProject, HtmlSplitter, pipeStreams, getOptimizeStreams, mergeStream, gulpFilter} = require('polymer-micro-build-toolbox');
const fs = require('fs');

// (1.)
const project = new PolymerProject({
  root: 'src/src/www',
  shell: 'components/vcms/vcms-shell.html'
});

const htmlSplitter = new HtmlSplitter();
const optimizeOptions = { css: { minify: true }, js: { minify: true }, html: { minify: true }};

// (2.)
let buildStream =  pipeStreams([
  mergeStream(project.sources(), project.dependencies()),
  htmlSplitter.split(),
  getOptimizeStreams(optimizeOptions),
  htmlSplitter.rejoin(),
  project.bundler(),
  gulpFilter(file => file.path !== project.config.entrypoint) // (3.)
]);

// (4.)
buildStream.on('data', file => {
  file.pipe(fs.createWriteStream('vcms-shell.min.html'));
}).on('end', _ => {
  console.log('build success');
});
  1. We create the project object. If we make the build from a parent directory, we need to inform the root directory. Or else the process will assume the index.html file is where we invoked the script.

  2. We use the pipeStreams function to start the building workflow. The pipeStreams needs to be used, trying to pipe() streams together will likely fail.

  3. We can use gulpFilter helper to remove the index.html file from the stream.

  4. Endpoint where we write the processed minified shell to a file.