Installing 10.3.x causes `typescript` to be pulled into the project as a dependency

[SimpleCreations]

Describe the bug
Starting with version 10.3.x, installing @storybook/react-native causes typescript to be automatically installed in node_modules. This is not desirable, for example, when the project is part of a monorepo where TypeScript is managed externally. React Native (even when TypeScript is used for sources) and most other 3rd party libraries do not depend on TypeScript.

TypeScript should not be a dependency of a 3rd party library. This bloats the project with an unnecessary TypeScript installation, and it may be not clear to tooling and developers which TypeScript version is the right one if the project already relies on a different TypeScript installation.

To Reproduce

1. Create a clean project
2. Install @storybook/react-native@10.2.3
3. Observe that typescript is not automatically added as a dependency
4. Upgrade to @storybook/react-native@10.3.1
5. Observe that typescript is added as a dependency

[dannyhw]

@SimpleCreations I looked at this and I believe its actually coming from @storybook/react I didn't add typescript here myself and its listed as a peer dependency in react-docgen-typescript

if this gets installed highly depends on what package manager you are using, however it should be overwritten if you have typescript in your own dependency list since its a peer

[SimpleCreations]

Hi @dannyhw, thank for the reply! Indeed the issue surfaced because @storybook/react-native depends on a new version of @storybook/react, which now depends on react-docgen-typescript. react-docgen-typescript has typescript listed as a runtime dependency (not peer). I use pnpm, but it should be the same regardless.

In my project, I don't have TypeScript installed directly. Instead, it is managed externally on the monorepo level, so ideally it shouldn't be installed at all on the subproject level. I ended up reverting @storybook/react-native back to 10.2.3.

Overall upgrading from 10.3 to 10.2 adds a lot of bloat to node_modules, and it would be nice if there was a way to reduce it. Maybe CLI tools could be separated from the @storybook/react-native runtime package? Then there would be no forced dependencies on development tools.

[dannyhw]

since this is not coming from the @storybook/react-native package its coming from @storybook/react, I can't make that change from this repo it needs to be raised on the main storybook repo