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

rollup-glob-opts

v0.1.0

Published

Helps maintaining many Rollup build targets by using file glob patterns.

Downloads

5

Readme

Expand Rollup Build Options by File Glob Patterns

NPM version Build Status Dependency Status devDependency Status

Helps maintaining many Rollup build targets by using file glob patterns. Reduces copying & pasting of options in the Rollup configuration.

Synopsis

Let us assume the following project structure with two components and their tests:

src/
├── first
│   ├── first.md
│   ├── first.ts
│   └── first.test.ts
└── second
    ├── second.md
    ├── second.ts
    └── second.test.ts

Rollup configuration usually contains options for building each component and each test:

export default [
  {
    input: 'src/first/first.ts',
    output: { file: 'dist/first.js' }
  },
  {
    input: 'src/second/second.ts',
    output: { file: 'dist/second.js' }
  }
  {
    input: 'src/first/first.test.ts',
    output: { file: 'src/first/first.test.js' }
  },
  {
    input: 'src/second/second.test.js',
    output: { file: 'src/second/second.test.js' }
  }
]

The copies of options for building components and their tests can be avoided by specifying each build target only once using file patterns with name placeholders delimited by square brackets:

import globOpts from 'rollup-glob-opts'

export default async () => [
  ...await globOpts({
    input: 'src/[name]/[name].ts',
    output: { file: 'dist/[name].js' }
  }),
  ...await globOpts({
    input: 'src/[name]/[name].test.ts',
    output: { file: 'src/[name]/[name].test.js' }
  })
]

The name placeholders in the input property are replaced with * and looked for in the local file system. One build options object is created for each pattern match.

The output property can point either to an object or to an array of objects, if multiple bundles are generated from one input.

Installation

You can install this package using your favourite Node.js package manager:

npm i -D rollup-glob-opts
yarn add -D rollup-glob-opts
pnpm i -D rollup-glob-opts

Debugging

If you need to investigate an unexpected behaviour of the file globbing, you can use the process environment, for example:

DEBUG=glob-opts rollup -c
...
  glob-opts expanding "src/[name]/[name].ts" +0ms
  glob-opts 4 files found for "src/*/*.ts". +1ms
  glob-opts matching "src/first/first.test.ts" with /^src\/([^/]+)\/([^/]+)\.ts$/ +0ms
  glob-opts dropping "src/first/first.test.ts", inconsistent "[name]": "first" != "first.test" +0ms
  glob-opts matching "src/first/first.ts" with /^src\/([^/]+)\/([^/]+)\.ts$/ +0ms
  glob-opts matching "src/second/second.test.ts" with /^src\/([^/]+)\/([^/]+)\.ts$/ +1ms
  glob-opts dropping "src/second/second.test.ts", inconsistent "[name]": "second" != "second.test" +0ms
  glob-opts matching "src/second/second.ts" with /^src\/([^/]+)\/([^/]+)\.ts$/ +0ms
  glob-opts 2 files matched "src/[name]/[name].ts". +0ms
  glob-opts matching "src/first/first.ts" with /^src\/([^/]+)\/([^/]+)\.ts$/ +0ms
  glob-opts new output "dist/first.js" for "dist/[name].js" +0ms
  glob-opts matching "src/second/second.ts" with /^src\/([^/]+)\/([^/]+)\.ts$/ +0ms
  glob-opts new output "dist/second.js" for "dist/[name].js" +0ms
...

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Lint and test your code using npm test.

License

Copyright (c) 2021-2024 Ferdinand Prantl

Licensed under the MIT license.