[Bug]: Builders with implicit imports break monorepos with multiple SB versions

[vanessayuenn]

Describe the bug

Our virtual entry files for both builder-webpack5 and builder-vite currently import from 'storybook' directly:

storybook/code/builders/builder-vite/src/codegen-modern-iframe-script.ts

Lines 119 to 126 in a8efe8f

	import { setup } from 'storybook/internal/preview/runtime';
	import '${SB_VIRTUAL_FILES.VIRTUAL_ADDON_SETUP_FILE}';
	setup();
	import { composeConfigs, PreviewWeb } from 'storybook/preview-api';
	import { isPreview } from 'storybook/internal/csf';

These imports are relative to the project root, which can lead to the wrong version of Storybook being loaded in monorepo setups that include multiple versions. We should update builders to not rely on implicit, relative imports, but instead only accept the resolved path.

[greptile-apps]

** Disclaimer** This information might be inaccurate, due to it being generated automatically
This issue requires modifying the import resolution in the virtual entry files for both builders: 1. In code/builders/builder-vite/src/codegen-modern-iframe-script.ts, replace direct imports from 'storybook' with resolved paths: ts // Replace import { composeConfigs } from '@storybook/preview-api'; // With import { composeConfigs } from '${resolvedStorybookPath}/preview-api'; 2. Add import resolution logic to both builders to determine the correct Storybook package path relative to the project being built. 3. Update the codegen functions to use these resolved paths when generating the virtual entry files. This will ensure the correct version of Storybook is loaded in monorepo setups with multiple versions.

About Greptile

This response provides a starting point for your research, not a precise solution.

Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

Edit Issue Bot Settings · Greptile