ghengeveld
commented
1 month ago @jeremydrichardson Could you run this minimal Node script, to check if the problem is how Execa runs that command? I could potentially expose the shell option.
#!/usr/bin/env node
import { execaCommand } from 'execa';
const buildCommand = 'yarn build-storybook'; // use your own
const run = async () => {
await execaCommand(buildCommand, {
shell: false,
preferLocal: true,
env: { CI: '1', NODE_ENV: 'production' },
stdout: 'inherit',
stderr: 'inherit',
});
};
run();Save this as run.mjs and run node run.mjs. You probably have to npm install execa first.
When this fails, see what happens when you change the shell and/or preferLocal options.
jeremydrichardson
Describe the bug
Bug report
I'm trying to use the Take snapshots feature in Storybook. When I click on the Take snapshots button in the Visual Tests tab of my local Storybook, it attempts to run a build but the build fails. The Chromatic snapshot then fails because it says Invalid Storybook build at ....
I looked through the
chromatic.logfile and found this command:So I enabled the Storybook log and found the following error in
build-storybook.log:Funny thing is if I run that same command manually from the command line it complete fine.
The only thing that might be unique about my setup is that we're running Storybook in a monorepo. Not sure if that would have an effect on Rollup having an error.
Thanks
To reproduce
I can't give a link because it's a private repo.
We have Storybook setup in a monorepo where it lives in the
/packages/workshopfolder. All the stories live in their respective packages in the/packagesfolder.Using Vite as our builder.
I'll try and give as much info as a can, though I can't share the repo as it's private and proprietary.
Environment