Allow to customize webpack plugins

[vitramir]

I am trying to get Elastic APM (elastic/apm-agent-nodejs) to work with ncc.

At this point the only solution I have found is the webpack plugin. Here is the thread regarding this issue.

Is it acceptable to add the ability to add custom webpack plugins? It violates the Zero configuration principe, but it may be acceptable to configure it when using a module, not CLI.

I can make PR for this feature

[lionelB]

@vitramir we use elastic apm with out bundle using this command

NODE_ENV=production node -r elastic-apm-node/start ./dist/index.js",

also, you will probably need to add other env variables to configure the apm client

[Zn4rK]

This would be a great feature! I'm happy to submit a PR for this!

[JustinFeng]

Any update on this? agreed, this will be a great feature if it can make require-in-the-middle work with vercel/ncc bundled js.

In our case, we are using Datadog(which under the hood use require-in-the-middle to auto-instrument varies packages), as of now, we have to give up on ncc bundling to benefit from the auto instrumentation, which is sadly a tradeoff

[styfle]

There is no plan to expose webpack internals/plugins because that would make it near impossible to migrate from webpack to the successor, turbopack. See https://turbo.build/pack

It violates the Zero configuration principle

Correct. I suggest forking this repo if you want to configure webpack.