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

babel-plugin-path-chunk-name

v1.3.1

Published

Babel plugin to transform import() with named chunk, and the chunk name is the path

Downloads

8,122

Readme

babel-plugin-path-chunk-name

Why we need this?

  • By default, webpack will generate dynamic chunks named with numeric value, say 0.js.
  • It's troublesome to add magic comments: webpackChunkName to every dynamic imports.
  • It's not easy to use webpack.NamedChunksPlugin.
  • Most of the time, we just want to keep the folder structure for dynamic chunks to easy debugging.

Installation

yarn

yarn add babel-plugin-path-chunk-name

npm

npm install babel-plugin-path-chunk-name

.babelrc:

{
  "plugins": ["path-chunk-name"]
}

What it does

Taking from the test snapshots, it does this:

import(/* webpackPrefetch: true */"./Foo")

      ↓ ↓ ↓ ↓ ↓ ↓

import(/* webpackPrefetch: true , webpackChunkName: 'Foo'*/"./Foo");

And if you're using dynamic imports:

import(`./base/${page}`)

      ↓ ↓ ↓ ↓ ↓ ↓

import(/* webpackChunkName: 'base/[request]' */`./base/${page}`);

And if with delay opts enabled


import(\\"./Foo\\")

      ↓ ↓ ↓ ↓ ↓ ↓

() => import(/* webpackChunkName: 'Foo' */"./Foo");

For more usages, please find the detail in ./__tests__/index.js

Options

delay: tells whether convert import expression to arrow function.

Say, import('./xxx') => () => import(/* webpackChunkName: 'xxx' */'./xxx')

But since 1.2.0 version, calling then method after importing will ignore lazy.

Say import('./xxxx').then(yyyy) => import(/* webpackChunkName: 'xxxx'*/'./xxxx').then(yyyy)

And since 1.3.0 version, if import is already in delay mode, say () => import('./foo')delay will do nothing.