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

lineman-vendor-split

v0.2.0

Published

A granular vendor/app bundle splitting plugin for Lineman

Downloads

7

Readme

lineman-vendor-split

Creates discrete vendor and app bundle files for js/css.

Installation

$ npm install lineman-vendor-split --save

What does this plugin do?

This plugin will configure your lineman project as follows:

  • grunt-concat-sourcemap: creates separate bundles

    • generated/{js,css}/vendor.{js,css}
    • generated/{js,css}/app.{js,css}
  • grunt-contrib-watch: watches the following files separately

    • files.{js,css}.app
    • files.{js,css}.vendor
  • asset-fingerprint: creates separate fingerprinted files

    • dist/{js,css}/vendor.{js,css}
    • dist/{js,css}/app.{js,css}
  • grunt-contrib-uglify: uglifies separate bundle files

    • generated/js/vendor.js
    • generated/js/app.js
  • grunt-cssmin: minifies separate bundle files

    • generated/css/vendor.css
    • generated/css/app.css
  • spec: prepends files.concatenatedVendor to the list of spec bundled files

        spec:
          files: [
            "<%= files.js.concatenatedVendor %>"
            "<%= files.js.concatenated %>"
            "<%= files.js.concatenatedSpec %>"
          ]

Why would I use this plugin?

You want to be able to emit <script src="app.js"> and <script src="vendor.js"> in lineman pages that live in pages/*.{us,html} for simplicity when debugging and more control over caching granularity. (Vendor bundles typically don't change all that much, so it's nice to avoid having to recompile/concat those dependencies if you don't have to).

Usage

Within pages/index.{us,html,hb} simply reference the separate bundles within script and link tags

Statically, like this:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>My App</title>
  <link rel="stylesheet" href="/css/vendor.css">
  <link rel="stylesheet" href="/css/app.css">
</head>
<body>
  <script src="/js/vendor.js"></script>
  <script src="/js/app.js"></script>
</body>
</html>

Or with your dynamic template of choice, ie: underscore using _.template

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>My Underscore Templated App Page</title>
  <link rel="stylesheet" href="<%= vendorcss %>">
  <link rel="stylesheet" href="<%= css %>">
</head>
<body>
  <script src="<%= vendorjs %>"></script>
  <script src="<%= js %>"></script>
</body>
</html>