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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@carlosjimenohernandez/vuebundler

v1.0.1

Published

Like simplebundler but using a *.js list file instead of a directory

Readme

vuebundler

Pack Vue.js (v2) components from CLI or API from a list of files. But no webpack or shit. Simple.

It can work in other more wide scenarios, because it just bundles all the .css, and all the .js together, injecting the .html files as string through $template first match in the .js.

But, you know. No webpack or shit.

Install

npm i -g @carlosjimenohernandez/vuebundler

Usage by CLI

vuebundler
  --list bundlelist.js
  --output dist/components.js
  --ignore file4.js file7.js file9.js
  --id MyCoolAPI
  --module false

Usage by API

require(__dirname + "/vuebundler.js").bundle({
    list: "bundlelist.js",
    output: "test/example1/dist/components.js",
    module: true,
    id: "Lib1",
    ignore: [],
});

While in bundlelist.js you have to provide something like:

module.exports = [
  __dirname + "/test/example1/lib/components/page1/page1",
  __dirname + "/test/example1/lib/components/page1/page2",
  __dirname + "/test/example1/lib/components/page1/page3",
];

Note that the .html, .js and .css extensions are omitted, as they MUST be these ones.

So, for each component we have, with their respective names:

  • page1.html
  • page1.js
  • page1.css

Everything is normal, except that in the .js you have to provide something like:

Vue.component("page-1", {
  name: "page-1",
  template: $template,
  props: {},
  data() {
    return {}
  },
  methods: {},
  watch: {},
  beforeCreate() {},
  created() {},
  beforeMount() {},
  mounted() {},
  beforeUpdate() {},
  updated() {},
  beforeDestroy() {},
  destroyed() {},
  activated() {},
  deactivated() {},
});

Note that template is filled with $template. The bundler pipes the text so it replaces the first $template match with the .html provided.

That is how the template component is injected in the logical component.

The bundler will take care to append all the JavaScript in a JavaScript file, and all the CSS in a CSS file.

The last step is to generate the output.js and output.css. The bundler uses the --output option as for the .js, and removes that same extension and appends the .css for the .css.

This way, only providing the .js name, the .css name is overstood.