[Feature]: Options for inline loaders

[dinofx]

What problem does this feature solve?

A "regular" loader can be passed options via module rules. For example:

rules:
    {
      test: [/\.tsx?$/, /\.js$/],
      loader: require.resolve('./my-loader'),
      options: {
        foo: 'bar',
      },
    },

But for an inline loader, there seems to be only one way to pass "options", and it involves polluting the LoaderContext namespace used by every loader. Example config:

{
  loader: {
    foo: 'bar'
  },
  …
}

The above "loader" config property does not scale well. Eventually two loaders will use the same loader property name, but define it to mean different things.

What does the proposed API of configuration look like?

Proposed:

resolveLoader: {
  alias: {
    'my-inline-loader': {
      loader: require.resolve('./my-inline-loader'),
      options: {
        foo: 'bar'
      }
    }
  }
}

[h-a-n-a]

Would you please try webpack to see if they support this?

[dinofx]

As far as I know webpack has a similar limitation, but webpack hasn't had a major release since 2020.

[hardfist]

As far as I know webpack has a similar limitation, but webpack hasn't had a major release since 2020.

@dinofx webpack still ships new feature in minor release, if it's not a breaking change it doesn't require a major release.