You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content from npm run build-module should be the same. It seems it isn't due to the use of temp directories to perform some compilation and then bundling. Ideally we should either not use temp directories (and keep the path constant) or tell its bundler to ignore the temp directory path part of each module's name when bundling, like we can with webpack (by providing it a context path).
This issue is causing a build problem when needing intel and arm resources for Brave on macos to be identical brave/brave-browser#38435
The text was updated successfully, but these errors were encountered:
The content from
npm run build-module
should be the same. It seems it isn't due to the use of temp directories to perform some compilation and then bundling. Ideally we should either not use temp directories (and keep the path constant) or tell its bundler to ignore the temp directory path part of each module's name when bundling, like we can with webpack (by providing it acontext
path).This issue is causing a build problem when needing intel and arm resources for Brave on macos to be identical brave/brave-browser#38435
The text was updated successfully, but these errors were encountered: