Should @storybook/react-native be installed as a dependency or a devDependency?

[mljlynch]

We have a repo where we import storybook/react-native and use it in our apps sandbox. We have all the dependencies installed in the devDependencies section, but the example app has these in the dependencies section. Is there guidance on where they should go?

[dannyhw]

it really doesn't really matter much how you do it, if you intend to ship an app to a user or have a storybook only app like for a design system you can make it a normal dependency.

In most cases a dev dependency is probably correct.

but im pretty sure it makes no actual practical difference unless you are running npm install --production

[mljlynch]

Thanks, we were having an issue where we had a pointer to storybook in our Sandbox screen stack, and one of the screens in that stack was our Storybook component, but that seems to be bloating the memory of the app, so we put it behind an environment variable. Is there a better way to do this?

{ENABLE_STORYBOOK === 'true' && (
        <SandboxStack.Screen
          name={SandboxScreen.Storybook}
          // eslint-disable-next-line @typescript-eslint/no-var-requires
          component={require('../../../.storybook/index').default}
        />
      )}

[dannyhw]

I think this is fine to do