Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

magic-comments-loader

Package Overview
Dependencies
Maintainers
1
Versions
24
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

magic-comments-loader

Add webpack magic comments to your dynamic imports during build time

  • 1.3.2
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
669
increased by237.88%
Maintainers
1
Weekly downloads
 
Created
Source

magic-comments-loader

Keep your source code clean, add magic coments to your dynamic import() statements at build time.

NOTE: This loader ignores dynamic imports that already include comments of any kind.

Magic comments supported:

Usage

First npm install magic-comments-loader.

Try not to have dynamic import() statements behind comments. It is better to remove unused code in production. If you must, e.g. your comment is referencing usage of dynamic imports, then these styles are ok:

// import('some-ignored-module')
/* Some comment about a dynamic import('module') */

If you must have a multiline comment then this style is ok (only one import() per comment line preceded by an asterisk):

/**
 * Comment about import('module/one')
 * Comment about import('module/two')
 * import('module/three'), etc.
 */

This module uses a RegExp not a parser. If you would like to add better support for ignoring import() behind multiline comments please open a pull request. See some more examples on regexr.

Configuration

Add this inside your webpack.config.js.

Without options

Adds webpackChunkName to all dynamic imports (same as webpackChunkName: true when using options).

module: {
  rules: [
    {
      test: /\.js$/,
      exclude: /node_modules/,
      use: ['magic-comments-loader']
    }
  ]
}
With options

The loader options is an object with keys corresponding to the names of supported magic comments. The following comments have a default behavior and do not require configuration beyond specifying where they should be applied (globally, or to certain files).

module: {
  rules: [
    {
      test: /\.js$/,
      exclude: /node_modules/,
      use: {
        loader: 'magic-comments-loader',
        options: {
          webpackChunkName: true,
          webpackMode: 'lazy',
          webpackIgnore: 'src/ignore/**/*.js',
          webpackPrefetch: 'src/prefetch/**/*.js'
          webpackPreload: [
            'src/preload/**/*.js',
            '!src/preload/skip/**/*.js'
          ]
        }
      }
    }
  ]
}
With config options

For more control, all comments support a configuration object with two supported keys, config and overrides. The config key is an object used to specifiy comment options. The overrides key is defined below.

All comments support a config.active key: Boolean | (modulePath, importPath) => Boolean. This is used to enable or disable the comment.

Here is an example of using config to customize comment behavior:

module: {
  rules: [
    {
      test: /\.js$/,
      exclude: /node_modules/,
      use: {
        loader: 'magic-comments-loader',
        options: {
          webpackChunkName: {
            config: {
              basename: true
            }
          },
          webpackMode: {
            config: {
              mode: 'lazy-once'
            }
          },
          webpackIgnore: {
            config: {
              active: false
            }
          }
        }
      }
    }
  ]
}
Overrides

You can also override the configuration passed in the config key by using overrides. It is an array of objects that look like:

overrides: [
 {
   files: ['src/**/*.js'],
   config: {
     active: true,
     mode: (modulePath, importPath) => {
       if (/eager/.test(importPath)) {
         return 'eager'
       }
     }
   }
 }
]

Here's a more complete example using config and overrides to customize how comments are applied:

module: {
  rules: [
    {
      test: /\.js$/,
      exclude: /node_modules/,
      use: {
        loader: 'magic-comments-loader',
        options: {
          verbose: true,
          webpackChunkName: {
            config: {
              basename: false
            },
            overrides: [
              {
                files: 'src/unique/**/*.js',
                config: {
                  basename: true
                }
              },
              {
                files: 'src/off/**/*.js',
                config: {
                  active: false
                }
              }
            ]
          },
          webpackPrefetch: [
            'src/prefetch/**/*.js',
            '!src/prefetch/skip/**/*.js'
          ],
          webpackMode: {
            config: {
              mode: 'lazy'
            },
            overrides: [
              {
                files: 'src/noMode/**/*.js',
                config: {
                  active: false
                }
              },
              {
                files: [
                  'src/**/*.js',
                  '!src/weak/**/*.js'
                ],
                config: {
                  mode: 'eager'
                }
              }
            ]
          }
        }
      }
    }
  ]
}

Magic Comments

With loader options configured like

  {
    loader: 'magic-comments-loader',
    options: {
      webpackChunkName: true,
      webpackPrefetch: 'src/some/module.js',
      webpackMode: 'eager'
    }
  }

an import statement inside src/some/module.js like

const dynamicModule = await import('./path/to/module.js')

becomes

const dynamicModule = await import(/* webpackChunkName: "path-to-module", webpackPrefetch: true, webpackMode: "eager" */ './path/to/module.js')

Options

These are the options that can be configured under the loader options. When using comments with a config key, you may also specify overrides.

  • verbose: Boolean. Prints console statements of the module filepath and updated import() during the webpack build. Useful for debugging your custom configurations.
  • match: String(module|import). Sets how globs are matched, either the module file path or the import() path. Defaults to 'module'.
  • webpackChunkName
    • true: Adds webpackChunkName comments to all dynamic imports. This is the default.
    • false: Disables adding the webpackChunkName comment globally.
    • ['/src/**/*.js']: Adds the comment when the glob(s) match a path from a match path.
    • Function: (modulePath, importPath) => String(<chunk name>). Returning false does not add the comment.
    • config.active: Boolean | (modulePath, importPath) => Boolean. Returning false does not add the comment.
    • config.basename: Boolean. Use only the basename from the import path as the chunk name. Relative imports may result in name collisions. Use in areas where you know the basenames are unique.
  • webpackPreload
    • true: Adds webpackPreload comments to all dynamic imports.
    • false: Disables adding the webpackPreload comment globally. This is the default.
    • ['/src/**/*.js']: Adds the comment with a value of true when the glob(s) match a path from a match path.
    • Function: (modulePath, importPath) => Boolean. Returning false does not add the comment.
    • config.active: Boolean | (modulePath, importPath) => Boolean. Returning false does not add the comment.
  • webpackPrefetch
    • true: Adds webpackPrefetch comments to all dynamic imports.
    • false: Disables adding the webpackPrefetch comment globally. This is the default.
    • ['/src/**/*.js']: Adds the comment with a value of true when the glob(s) match a path from a match path.
    • Function: (modulePath, importPath) => Boolean. Returning false does not add the comment.
    • config.active: Boolean | (modulePath, importPath) => Boolean. Returning false does not add the comment.
  • webpackIgnore
    • true: Adds webpackIgnore comments to all dynamic imports. You don't want to do this.
    • false: Disables adding the webpackIgnore comment globally. This is the default.
    • ['/src/**/*.js']: Adds the comment with a value of true when the glob(s) match a path from a match path.
    • Function: (modulePath, importPath) => Boolean. Returning false does not add the comment.
    • config.active: Boolean | (modulePath, importPath) => Boolean. Returning false does not add the comment.
  • webpackMode
    • true: Adds webpackMode comments to all dynamic imports using lazy.
    • false: Disables adding the comment globally. This is the default.
    • String(lazy|lazy-once|eager|weak): Adds the comment to all dynamic imports using the provided value.
    • Function: (modulePath, importPath) => String(lazy|lazy-once|eager|weak). Return falsy value to skip.
    • config.active: Boolean | (modulePath, importPath) => Boolean. Returning false does not add the comment.
    • config.mode: String(lazy|lazy-once|eager|weak) | (modulePath, importPath) => String(lazy|lazy-once|eager|weak). Return falsy value to skip.
  • webpackExports
    • Function: (modulePath, importPath) => [String(<module names|default>)]. Return falsy value to skip.
    • config.active: Boolean | (modulePath, importPath) => Boolean. Returning false does not add the comment.
    • config.exports: (modulePath, importPath) => [String(<module names|default>)]. Return falsy value to skip.

Keywords

FAQs

Package last updated on 13 Sep 2021

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc