refactor: remove nodejs module `util`

[hustcc]

• [x] remove util module, make tapable can be run on browser
• [x] remove browser configure in package.json, becaure all code can be run on nodejs and browser

to avoid error below in webpack 5:

[linux-foundation-easycla[bot]]

The committers are authorized under a signed CLA.

• :white_check_mark: hustcc (78880733ff2a3aa742b368bd32922609cdc837e8)

[alexander-akait]

We already supports browser https://github.com/webpack/tapable/blob/master/package.json#L31

[hustcc]

We already supports browser https://github.com/webpack/tapable/blob/master/package.json#L31

not valid config for webpack 5.

---

There is only 1 api which is from nodejs util. There is absolutely no need to use built-in modules, and then modify the building config for browsers.

The right way is remove the built-in module and directly use the polyfill code.

[hustcc]

Now, we solve it by below code, very dirty.

module.exports = {
  mode: 'production',
  entry: './src/index.ts',
  output: {
    library: 'Spreadsheet',
    libraryTarget: 'umd',
    filename: 'spreadsheet.min.js',
  },
  resolve: {
    extensions: ['.ts', '.tsx', '.js'],
    fallback: {
      // use polyfill util code from `tapable`
      util: require.resolve('tapable/lib/util-browser.js'),
    },
  },
  plugins: [
  ],
  module: {
    rules: [
      { test: /\.tsx?$/, loader: 'ts-loader' }
    ]
  },
  externals: {
  },
};

[alexander-akait]

The right way is remove the built-in module and directly use the polyfill code.

No, I can't reproduce your problem... Maybe you can provide full example?

[hustcc]

The right way is remove the built-in module and directly use the polyfill code.

No, I can't reproduce your problem... Maybe you can provide full example?

I have no time to provide full example. In terms of code rationality, the best way to support the browser is to delete util, to avoid the dependence of build configure.

I can support browsers directly. Why do I need to rely on building?

[hustcc]

way to reproduce:

• create pkg A dependence tapable, then release it with esm cjs
• create pkg B dependence A, then build umd with webpack

"ts-jest": "^24.3.0",
"ts-loader": "^9.2.6",
"typescript": "^4.4.2",
"webpack": "^5.64.4",
"webpack-cli": "^4.9.1"

[alexander-akait]

Why do your bundle tapable? Do you use it in your application?

[hustcc]

Why do your bundle tapable? Do you use it in your application?

antv/g depends on tapable, I am using antv/g to dev an module which should be used in browser by script.

[alexander-akait]

There is only one problem - tracking depredations on Node.js using CLI, but I think it is not real problem...