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

named-exports

v0.9.0

Published

Webpack plugin to make named exports

Downloads

10

Readme

named-exports

Generates named exports in real time from one or more directories.

Getting Started

To begin, you'll need to install named-exports:

$ npm install named-exports --save-dev

Se você quer exportar arquivos dentro da pasta de componentes

├── src
│   └── components
│       ├── ButtonStyled.vue
│       ├── InputStyled.vue
│       └── ...
...

Then add the plugin to your webpack config. For example:

webpack.config.js

const NamedExports = require('named-exports')

module.exports = {
  plugins: [
    new NamedExports({
      patterns: [
        {
          paths: ['src/components']
        }
      ]
    })
  ]
}

Result:

src/components/index.js
export { default as ButtonStyled } from './ButtonStyled.vue'
export { default as InputStyled } from './InputStyled.vue'
// ..

Options

const NamedExports = require('named-exports')

module.exports = {
  plugins: [
    new NamedExports({
      patterns: [
        {
          basePath: 'src',
          paths: ['components/**/', 'store/**', 'utils'],
          includeFolders: true,
          indexOfFolders: 'index.vue',
          ignore: ['*.css'],
          output: {
            filename: 'index.ts',
            comment: true,
            semi: true,
            singleQuote: true,
            finalNewLine: false
          }
        }
      ]
    })
  ]
}

Pattern

| Name | Type | Default | Description | | :-------------------: | :----------------: | :-------------: | :---------------------------------------------------------------------------------------------------- | | basePath | {String} | undefined | Base for all paths, the goal is to avoid repetition. | | paths | {Array} | undefined | All target paths that need an export file. | | includeFolders | {Boolean} | false | Determines whether to include folders in exports. | | indexOfFolders | {String} | undefined | sometimes index.js is not an index of a folder we want to export, so use this property to define. | | ignore | {Array} | ['.DS_Store'] | Files or folders to be ignored. | | output.filename | {String} | index.js | Name of the export file that will be generated in each defined path. | | output.comment |{Boolean\|String} | false | Comment to make it explicit that the file was automatically generated by a plugin. | | output.semi | {Boolean} | false | Put semicolons at the end of each export. | | output.singleQuote | {Boolean} | true | Use single quotes in the export code | | output.finalNewLine | {Boolean} | true | Insert a blank line at the end of the export file, just to maintain the beauty standard of your app. |

ℹ️ If you need exports with different settings in another folder, you can add as many patterns as you want.

ℹ️ named-exports is not designed to exports files generated from the build process; rather, it is to exports files that already exist in the source tree, as part of the build process.

Documentation

Read the documentation and demos.

License

MIT