Reference `webpack.DefinePlugin` in the readme

webpack.DefinePlugin offer a native way to run simple replacements, which covers the first example.

I can open a PR that adds a link to this issue as documentation in the readme, and add more examples, including dynamic ones like https://github.com/sindresorhus/refined-github/commit/130c110b0645603a4c19e078064ff293d4a69fc0

With this loader

module.exports = {
  module: {
    rules: [
      {
        test: /fileInWhichJQueryIsUndefined\.js$/,
        loader: 'string-replace-loader',
        options: {
          search: '$',
          replace: 'window.jQuery',
        }
      }
    ]
  }
}

With DefinePlugin

module.exports = {
  plugins: [
    new webpack.DefinePlugin({
      $: 'window.jQuery'
    })
  ]
}

[Va1]

as i mentioned in the previous comment, string-replace-loader is a loader on contrast to DefinePlugin being a plugin. this means, that it can be used for specific files via regex (as loaders are defined with test property) and, what’s more important, in specific positions in the loader chain (before loader A does it’s job, but over results loader B has produced, if defined between em).

this, i believe, makes both just different tools, use-cases of which intersect but are not equal by any means. which invalidates the “why 3rd party loader” question, in my opinion. examples defined in readme are plain variable replacement ones, but this does not deny the point i wrote above, as well as does not mean that more complex examples should be added to justify its existence (or does it? and does this module lack examples overall?).

what may be a justified thing to do is to reference the DefinePlugin in a form like “yo btw, if what you’re doing is a simple & global variable replacement, you may be able to achieve it via DefinePlugin, read more here”. but the emphasis on examples seems a bit over the top to me (i might be wrong tho).

[pietia]

I’ve refactored my project so that i can use DefinePlugin , so - case closed.