How to use "browser" package.json field in static (Node) build? about batfish HOT 2 CLOSED

The specific reason I'm seeing this is one library (got) that conditionally calls require('electron') — but Webpack can't know that it doesn't need to bundle 'electron' in there. So I have a PR to add electron to the externals list during the static build, and maybe that will be enough to address this problem, at least for now.

from batfish.

I wonder if the only reason we can't use a regular, non-target: node Webpack build is because static-render-pages.js uses fs and path. If that's the case, a better long-term solution might be to revise the static build system so that those requirements exist outside the code that Webpack bundles up.

from batfish.