Open thejuan opened 4 years ago
When enabling SSR dependencies can be brought into the server side package which aren't compatible with the FAB VM. These aren't actually needed server side so I can exclude them in the next build using
webpack: (config, options) => { const { isServer } = options; if (isServer) { config.externals.push("aws-amplify"); } return config; },
Despite not being anywhere in the next build, they still seem to get pulled into the FAB built code.
Example repo https://github.com/Hatch-Team/fab-build-issues/tree/issues/301
When enabling SSR dependencies can be brought into the server side package which aren't compatible with the FAB VM. These aren't actually needed server side so I can exclude them in the next build using
Despite not being anywhere in the next build, they still seem to get pulled into the FAB built code.