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 🙏

© 2026 – Pkg Stats / Ryan Hefner

main-yarn-files

v3.0.4

Published

Get main files from your installed yarn packages.

Readme

main-yarn-files

status npm version

This plugin only works with gulp (feel free to add grunt support). This plugin is a replacement for the main-bower-files plugin when migrating from bower to yarn, with less options, and it will only list modules declared in dependencies and not the ones delcared in devDependencies.

Installation

with npm: npm install main-yarn-files

with yarn: yarn add main-yarn-files

Usage

var mainYarnFiles = require('main-yarn-files');
var files = mainYarnFiles([[filter, ]options][, callback]);

If first argument is type of String, Array or RegExp it will be used as a filter, otherwise it will be used as options.

This will read your package.json, iterate through your dependencies and returns an array of files defined in the main property of the packages package.json if not found it will check for bower.json, .bower.json and component.json.

You can override the behavior if you add an overrides property to your own package.json.

Usage with gulp

var gulp = require('gulp');
var mainYarnFiles = require('main-yarn-files');

gulp.task('TASKNAME', function() {
    return gulp.src(mainYarnFiles())
        .pipe(/* what you want to do with the files */)
});

You've got a flat folder/file structure after .pipe(gulp.dest('my/dest/path'))?

mainYarnFiles returns an array of files where each file is a absolute path without any globs (** or *). gulp requires globs in these paths to apply the base path. Because of this, you always have to tell gulp your dependencies base path (the path to the node_modules/@bower_components directory) explicitly.

Here is an example:

var gulp = require('gulp');
var mainYarnFiles = require('main-yarn-files');

gulp.task('TASKNAME', function() {
    return gulp.src(mainYarnFiles(/* options */), { base: 'path/to/node_modules/@bower_components' })
        .pipe(/* what you want to do with the files */)
});

Or:

gulp.task('TASKNAME', function() {
    return gulp.src(mainYarnFiles({
			paths: {
				modulesFolder: nrhSrc + '/bower_components'
			}
		}))
        .pipe(/* what you want to do with the files */)
});

Now you should get something like my/dest/path/jquery/jquery.js if you have jquery installed.

Options

Overrides Options

ignore

Type: Boolean Default: false

Set to true if you want to ignore this package.

dependencies

Type: Object

You can override the dependencies of a package. Set to null to ignore the dependencies.

Common Options

These options can be passed to this plugin, e.g: mainYarnFiles(/* options*/)

debugging

Type: boolean Default: false

Set to true to enable debugging output.

main

Type: String or Array or Object Default: null

You can specify for all packages a default main property which will be used if the package does not provide a main property.

env

Type: String Default: process.env.NODE_ENV

If process.env.NODE_ENV is not set you can use this option.

paths

Type: Object or String

You can specify the paths where the following yarn specific files are located:

node_modules/@bower_components and package.json

For example:

mainYarnFiles({
    paths: {
        modulesFolder: 'path/for/node_modules/@bower_components',
        jsonFile: 'path/for/package.json'
    }
})
.pipe(gulp.dest('client/src/lib'));

If a String is supplied instead, it will become the basepath for default paths.

For example:

mainYarnFiles({ paths: 'path/for/project' });
/*
    {
        modulesFolder: 'path/for/node_modules/@bower_components',
        jsonFile: 'path/for/package.json'
    }
*/

checkExistence

Type: boolean Default: false

Set this to true if you want that the plugin checks every file for existence.

If enabled and a file does not exists, the plugin will throw an exception.

filter

Type: RegExp or function or glob Default: null

You can filter the list of files by a regular expression, glob or callback function (the first and only argument is the file path).

LICENSE

(MIT License)

Copyright (c) 2013 Christopher Knötschke [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.