How to prevent webpack from ever parsing some .js file

[Knagis]

We are using a third party .js library in our project - the file is large, and is minified and obfuscated. We would like to output it as is - without running any processing on it.

Disabling minification is straight forward - in our case using exclude in the for terser-webpack-plugin. We do need to do that since either terser or swc minification actually breaks the obfuscated code...

However, with minification disabled we see that what was originally minified code is now "pretty-printed", with newlines and whitespaces.

I tried setting module.noParse - that has no effect. Tried setting Rule.parser = false - that crashes the compilation.

I can't use simply copy-file approach since i do want to import() to include the file in the project (it has no exports, just side effects) and thus i need webpack to add its own chunk loading wrapper around it.

Is such pass-through of JS code supported somehow?

[alexander-akait]

module.noParse should work, we just don't parse this file and so include as is, can you show me an example using github?

[Knagis]

Eh, my bad... noParse does indeed work. Sorry, I should have tried reproducing it in isolation first..

Where i made a mistake is i added a module.rules entry matching my file, specifying just the type: "javascript/auto" but didn't think of adding exclude on my actual .js rule.. I keep thinking that first matched rule stops the iteration through the reminder, while that is only true within oneOf

So it ended up being swc-loader that picks up the file and parsed it..

[alexander-akait]

Yeah, chaining it will be a big breaking change, we a things to introduce in future glob (also os neutral slashes) as an alternative of test and make it - that first matched rule stops, but it is under discussion right now