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

node-require-webpack-plugin

v0.1.1

Published

为 node.js 环境下的 webpack 打包结果提供动态 require 支持。

Downloads

7

Readme

node-require-webpack-plugin

为 node.js 环境下的 webpack 打包结果提供动态 require 支持。

为什么要使用

在某些情况下,我们需要让 webpack 打包的文件在 node.js 环境下运行,例如 GitHub Action 的开发,但是会有一些问题:

const a = require(process.argv)

上面的代码中,我们动态 require 了用户传入的参数,但 webpack 并不知道 -- 在 build 时它会尝试寻找 process.argv 的值并读取其内容以供打包,这很明显是无法做到的。

因此在我们执行打包后的代码时会得到 module not found 异常。

用法

首先安装依赖:

npm install node-require-webpack-plugin -D

添加 plugin 配置到 webpack.config.js:

module.exports = {
  plugins: [
    new NodeRequireWebpackPlugin()
  ]
}

如果你的项目基于 ts-loader,请将 transpileOnly 置为 true

  module: {
  rules: [
    {
      test: /\.tsx?$/,
      loader: 'ts-loader',
      options: {
        transpileOnly: true
      }
    }
  ]
}

在你需要动态 require 的语句前增加 /*#__PURE_REQUIRE__*/ 标记,例如:

const requireResult =  /*#__PURE_REQUIRE__*/ require(`${configPath}`);

工作原理

  • 将所有用户标记 /*#__PURE_REQUIRE__*/ 的模块全部换成一个函数 __WEBPACK_PURE_REQUIRE__
  • 为每个入口文件添加 __WEBPACK_PURE_REQUIRE__ 的实现:
function __WEBPACK_PURE_REQUIRE__(content) {
  /******/
  return require(content)
}