Hey Aaron, super sorry to be so slow to follow up! I think that in the deploy you link, the build failed, based on this message:
11:37:52 AM: ./src/components/Tables/fundSummaryTable/fundSummaryColumns.js 83:12
11:37:52 AM: Module parse failed: Unexpected token (83:12)
11:37:52 AM: File was processed with these loaders:
11:37:52 AM: * ./node_modules/babel-loader/lib/index.js
11:37:52 AM: You may need an additional loader to handle the result of these loaders.
11:37:52 AM: | var id = _ref2.id;
11:37:52 AM: | return id === "".concat(row.id);
11:37:52 AM: > }))?.["total_profit"] || 0) > 0;
11:37:52 AM: | },
11:37:52 AM: | style: {
11:37:52 AM: @ ./src/components/Tables/fundSummaryTable/FundSummaryTable.jsx 13:0-47 111:13-20
11:37:52 AM: @ ./src/routes/overview/Overview.jsx
11:37:52 AM: @ ./src/routes/overview/index.jsx
11:37:52 AM: @ ./src/routes/index.jsx
11:37:52 AM: @ ./src/App.jsx
11:37:52 AM: @ ./src/index.jsx
…that perhaps your build failed, but did not “tell the system” that it failed, by returning a non-zero exit code from the master process which I think at that point was likely npm run build:server. Perhaps some subprocess doesn’t pass the exit code back up to npm, or npm ignores it? webpack --bail is an example of a subprocess that WILL return errors to us, while plain webpack doesn’t necessarily pass the error back up to its caller.