The builds always seems to stall out at around 67-69% (when building components from react-feather, not sure if that’s relevant), and I get “Build script returned non-zero exit code: 1”.

The weird thing is deploying this Storybook used to work just fine. The only thing that changed when it started to break was importing SVGs as React components. Here’s an example of an offending line: import { ReactComponent as BackDisplay } from '../../assets/logo.svg';. This actually gave me a Typescript “module not found” error during one ill-fated Netlify deploy, but I never saw it again lol, now I just get the 67% stall outs.

Anyway, here’s the last section of the deploy output before it just stops cold; oh, and the npm run build-storybook command works fine locally:

Hi @backpackless - could you try turning off the verbose mode in storybook/webpack to see if that allows more useful logs to be shown before your build aborts? you’d specifically want to remove the --progress flag to webpack if you call it directly, and add --quiet flag to storybook if that’s what you call instead.

I think that will expose the actual failure logs for you but let me know if not!

For some reason importing an SVG as a React component isn’t working on Netlify but is working locally. I’m pretty sure the import { ReactComponent as Icon } from './icon.svg' is part of the Create React App webpack setup, but I’m not sure why this feature wouldn’t carry over to the deploy.