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

vitruvius

v3.0.0

Published

Master builder for Lerna projects.

Downloads

25

Readme

vitruvius Build Status Windows Build Status npm version

Master builder for Lerna projects.

  • Transpile source code with Babel, excluding tests
  • Copy non-JS assets to the output directory

Getting Started

Install vitruvius using npm:

npm install --save-dev vitruvius

Next add a simple npm script to run vitruvius:

"scripts": {
    "build": "vitruvius build --src src --dest lib"
}

Now, running npm run build will look in the src directory of each package in your project and output the compiled code in a lib folder in each package.

Usage

vitruvius build --src <srcDirName> --dest <destDirName> [--ignore <fileGlobPatterns>]

src (required) is the name of the source directory within each package.

dest (required) is the name of the output directory you want to create in each package.

ignore-packages (optional) is an array of glob patterns for packages to ignore.

ignore-files (optional) is an array of glob patterns for files and directories to ignore. By default, *.test.js, *.spec.js, **/__tests__/**, and **/__mocks__/** are ignored.

As a point of reference, let's consider this standard Lerna project:

my-lerna-repo/
  packages/
    package-1/
      src/
        index.spec.js
        index.js
      package.json
    package-2/
      src/
        data.json
        index.js
      package.json

Let's say we want to compile the source code in package-1 and package-2 into a lib folder.

To do this, we can run vitruvius build --src src --dest lib. This will Babel compile the source code, copy any non-JS files, and ignore test files.

After building, our project now looks like this:

my-lerna-repo/
  packages/
    package-1/
      lib/
        index.js
      src/
        index.spec.js
        index.js
      package.json
    package-2/
      lib/
        data.json
        index.js
      src/
        data.json
        index.js
      package.json

As you can see, package-1/src/index.js has been compiled into package-1/lib/index.js, while package-1/src/index.spec.js was ignored. And package-2/src/data.json was copied over to package-2/lib/data.json, along with package-2/src/index.js being compiled to package-2/lib/index.js.