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-generate-entry

v1.0.1

Published

A Rollup plugin for component libary code splitting

Downloads

2

Readme

rollup-generate-entry

A Rollup plugin for component libary code splitting

Install

Use yarn or npm to manage your package

npm install rollup-generate-entry --save-dev
#or
yarn add rollup-generate-entry --dev

Why

When we try to create a component libary project and have the directory like this

src
|
|--componentA
|
|--componentB
|
|--index.tsx
...

This plugin can generate entry file in output directory by traversing folder in component directory, we can complie product of the same structure in rollup, and need a entry file to export the splitted component for effect of tree shaking, but it always pack a file which include all componentent through the entry file that like index.tsx.

Usage

Import the plugin in rollup.config.js

import GenerateEntry from 'rollup-generate-entry';

export default [{
  input: 'main-a.js',
  output: {
    file: 'dist/bundle-a.js',
    format: 'cjs'
  },
  plugins: [GenerateEntry()]
}, {
  input: 'main-b.js',
  output: [
    {
      file: 'dist/bundle-b1.js',
      format: 'cjs'
    }
  ],
  plugins: [GenerateEntry()]
}];

Perhaps, you can use rollup-plugin-multi-entry to support multiple input files

Options

target

Type: String
Default: '/dist'

root

Type: String
Default: '/src'

exclude

Type: Array<string>
Default: ['componentA']

Ignore some folder in component directory

namingRule

Type: String Default: ''

The naming rules of export component