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

@zenstone/webpack-starter

v1.0.7

Published

一个更简易的 Webpack 启动器。

Downloads

27

Readme

@zenstone/webpack-starter

一个更简易的 Webpack 启动器。

pnpm add typescript @zenstone/webpack-starter @types/react @types/react-dom webpack webpack-dev-server webpack-cli -D
pnpm add react react-dom

添加 webpack.config.js 文件

const Starter = require('@zenstone/webpack-starter');

// 未指定,默认取以下值
// root   = process.cwd()
// entry  = main: root/src/index.[ts|tsx|js|jsx]
// html   = root/src/index.html
// output = root/dist

module.exports = function(runtime) {
  // 默认 entry process.cwd()/src/index.[ts|tsx|js|jsx]
  return Starter.create({ 
    runtime,
    onBuildExit: {
      scripts: [
        () => {
          console.log('build exit');
        },
      ],
      parallel: false,
      blocking: true,
    },
    copy: {
      patterns: [
        { from: 'source', to: 'dest' },
        { from: 'other', to: 'public' },
      ],
    },
  }).setDevServer(devServer => {
    devServer.open = true;
    devServer.compress = true;
    devServer.historyApiFallback = true;
    return devServer;
  }).export(console.log);
};

启动参数

type WebpackRuntime = {
  WEBPACK_BUNDLE?: boolean;
  WEBPACK_BUILD?: boolean;
  WEBPACK_SERVE?: boolean;
};

type WebpackStarterOptions = {
  // 应用名称
  appName?: string;
  // webpack 运行模式 development | production ,去掉 none
  mode?: WebpackMode;
  // 工作根目录,默认取 process.cwd() ,也就是 package.json 所在目录
  root: string;
  // webpack 的运行时参数
  runtime: WebpackRuntime;
  // 入口配置快捷方式,参考 webpack.config.entry :https://webpack.js.org/concepts/entry-points/
  entry?: WebpackEntry;
  // copy-webpack-plugin 快捷配置入口:https://www.npmjs.com/package/copy-webpack-plugin
  copy?: WebpackCopyPluginOptions;
  // webpack-shell-plugin-next 快捷配置入口::https://www.npmjs.com/package/webpack-shell-plugin-next
  shell?: WebpackShellPluginOptions;
  // js 路径前缀,默认为指定,即 main.js
  jsPath?: string;
  // css 路径名前缀,默认未指定,即 main.css
  cssPath?: string;
  // 图片路径名前缀,默认 images,即 images/1.jpg
  imgPath?: string;
  // 其他文件路径名前缀,默认 files,即 files/xxx.txt
  filePath?: string;
  // 参考 webpack.devServer.historyApiFallback :https://webpack.js.org/configuration/dev-server/#devserverhistoryapifallback
  historyApiFallback?: WebpackDevServerConfiguration['historyApiFallback'];
  // 参考 webpack.devServer.proxy :https://webpack.js.org/configuration/dev-server/#devserverproxy
  proxy?: WebpackDevServerConfiguration['proxy'];
};

Loaders 管理

const Starter = require('@zenstone/webpack-starter');

const starter = Starter.create({});

// 以一个 map 进行注册
// Record<string, RuleSetRule>
starter.loaders = {
  svg: starter.svgrLoader(),
  img: starter.imgAsset(),
  swc: starter.swcLoader(),
  css: starter.cssLoader(/\.css$/, /\.module\.css$/),
  cssModule: starter.cssLoader(/\.css$/, /\.module\.css$/, {
    cssModule: true,
  }),
  file: starter.fileLoader(),
};
// 以一个 strong[] 来维护先后顺序和是否使用
starter.useLoaders = ['svg', 'img', 'swc', 'css', 'cssModule', 'file'];

// 你可以自行注册一个 Loader ,如
starter.loaders.babel = {
  test: /\.(?:js|mjs|cjs)$/,
  exclude: /node_modules/,
  use: {
    loader: 'babel-loader',
    options: {
      presets: [
        ['@babel/preset-env', { targets: 'defaults' }],
      ],
    },
  },
};

// 将 swc 替换为 babel
starter.useLoaders[2] = 'babel';

Plugins 管理

const Starter = require('@zenstone/webpack-starter');

const starter = Starter.create({});

// 插件以一个 map 进行注册,需要使用的插件,可自行添加或者移除。
// Record<string, WebpackPluginInstance>
starter.plugins;

// 移除 case-sensitive-paths-webpack-plugin 插件
delete (starter.plugins.caseSensitive);

// 插件不额外通过数组进行管理,直接通过 Object.values(this.plugins).filter(Boolean)
// 具体亦可通过继承 Starter 类,重载 buildPlugins 做更多的处理

Optimization 说明

在 Starter 初创建的时候,默认的 optimizationundefined

const Starter = require('@zenstone/webpack-starter');

const starter = Starter.create({});

// undefined
console.log(optimization);

// 过程中可自行控制以下内容
// 默认情况下,minimize 只在非 devel 模式下为 true
starter.minimize = !starter.isDevel;
// minimizer 
// js 绑定了 terser-webpack-plugin : https://www.npmjs.com/package/terser-webpack-plugin
// css 绑定了 css-minimizer-webpack-plugin : https://www.npmjs.com/package/css-minimizer-webpack-plugin
starter.minimizer = [];
// 默认无值
// 参考 webpack.optimization.splitChunks : https://webpack.js.org/plugins/split-chunks-plugin/#optimizationsplitchunks
starter.splitChunks = {};

// 直到调用 export 方法时,才会调用 buildOptimization 去生成 optimization 的结构。
// 即用户可在 buildOptimization 之前,通过 starter 属性的方式直接修改相关设定
// starter.buildOptimization() 不会写入本地 optimization 属性,每次都会合并成一个新的 optimization object
starter.export();

Issues

@babel/core 的引用

@svgr/webpack@svgr/core 目前依赖于 @babel/core ,暂无替代方案。

.swcrc 父目录的影响

├── packages
│   └── app
│       ├── **/*.[ts|tsx]
│       └── webpack.config.js
├── .swcrc (1)
└── .gitignore

目前为了简化 webpack 的目录结构,将 swc 的配置放入了 loader 中,如:

const swcLoaderOptions = {
  jsc: {
    parser: {
      syntax: 'typescript',
      tsx: true,
      // jsx: true,
      decorators: true,
      dynamicImport: true,
    },
    loose: false,
    externalHelpers: true,
    transform: {
      legacyDecorator: true,
      decoratorMetadata: true,
      optimizer: {
        simplify: true,
      },
      react: {
        runtime: 'automatic',
        importSource: 'react',
        refresh: this.isDevel,
      },
    },
  },
  env: {
    targets: ['defaults'],
    mode: 'entry',
    coreJs: '3',
  },
  sourceMaps: true,
};

但目前版本的 swc-loader ,假定目录内存在 .swcrc (1) 文件,会将 .swcrc (1) 和 swcLoaderOptions 的配置进行合并。

所以如果 .swcrc (1) 中定义了 jsc.target ,则会导致启动 webpack 时,报错 jsc.targetenv.targets 不能同时存在。

解决的办法,是在子项目目录额外添加一个 .swcrc (2) 文件,结构如下:

├── packages
│   └── app
│       ├── **/*.[ts|tsx]
│       ├── .swcrc (2)
│       └── webpack.config.js
├── .swcrc (1)
└── .gitignore

确保 .swcrc (2) 的内容,为符合 webpack 运行所需的配置即可。