build-storybook not exiting once finished for React

Note: This was probably a self-imposed bug due to a bad webpack config in our ./storybook directory. Issue has been closed.

Describe the bug When running build-storybook from a react app, it does not exit after the build completes. I believe you need to implement the following fix https://github.com/storybookjs/storybook/commit/9389325c80373d9cd96c2845d39e0b46ba2a7b16 so that the command will exit correctly for react storybook. (This should be implemented for all other languages, the original fix was committed only for angular for some reason…) Otherwise, the build-storybook command stops after the info => Output directory: step and hangs there. This blocks a lot of processes, such as Chromatic, that utilize this command.

To Reproduce Run build-storybook with the latest storybook packages in a react app and witness the script not exiting once completed. It is easy to see via the below code snippet that there is no way for the buildStatic method to exit without the code within the “**”, and will therefore continue the build-storybook command running indefinitely until killed by another process.

System The command build-storybook will not exit after reaching the output of info => Output directory: x/y/z

Additional context You can circumvent this locally by adding process.exit(0) to the buildStatic method in node_modules/@storybook/core-server/dist/cjs/build-static.js

async function buildStatic(_ref2) {
  var packageJson = _ref2.packageJson,
      loadOptions = _objectWithoutProperties(_ref2, ["packageJson"]);

  var cliOptions = (0, _cli.getProdCli)(packageJson);

  try {
    await buildStaticStandalone(_objectSpread(_objectSpread(_objectSpread({}, cliOptions), loadOptions), {}, {
      packageJson: packageJson,
      configDir: loadOptions.configDir || cliOptions.configDir || './.storybook',
      outputDir: loadOptions.outputDir || cliOptions.outputDir || './storybook-static',
      ignorePreview: (!!loadOptions.ignorePreview || !!cliOptions.previewUrl) && !cliOptions.forceBuildPreview,
      docsMode: !!cliOptions.docs,
      configType: 'PRODUCTION',
      cache: _coreCommon.cache
    }));
    **process.exit(0);**
  } catch (e) {
    _nodeLogger.logger.error(e);

    process.exit(1);
  }
}