How to exclude node_modules from compilation?

[suhdonghwi]

Hi,

First of all, thank you for this very useful plugin - it has been a great help.

I’m currently using @stylexswc/nextjs-plugin. I noticed that when using the Next.js plugin, it ends up compiling every .js(x) file under node_modules as well.

When using @stylex/babel-plugin, it’s possible to pass an exclude option through webpack rules to avoid this(Example). With this plugin, there isn’t a way to do that, because it doesn't expose a webpack plugin directly; it provides a config transformer that manipulates the webpack configuration.

Is there a way to exclude dependencies in node_modules from being compiled? If not, I'd be happy to contribute - could you share any guidance on how you'd prefer this to be implemented, or what direction would make sense for the project?

Thanks!

[Dwlad90]

Hi @suhdonghwi ,
Thank you for your interest in the project.

I don't think this is quite correct behavior. As far as I know, the NextJS plugin doesn't transpile files from node_modules by default. Therefore, for example, to transpile the @stylexjs/open-props package, you need to define it via the transpilePackages parameter in next.config.js. You can see an example here, and here's a link to the official documentation. I might be wrong or don't fully understand your use case, so it would be better to get a minimal replication of this behavior.

For better debugging, you can log a list of all transpiled files in the console by defining the STYLEX_DEBUG=info environment variable.

If you have any ideas on how to solve your problem and improve the plugin, I'm open to pull requests.