---
title: "Comment by Hayata Suenaga on \"Using Storybook with Expo Router v2, SDK 49 & TypeScript\" | Hashnode"
description: "I really enjoyed the article, and it was very helpful in getting started with setting up Storybook in my Expo project. Now, as I'm trying to create a produc"
url: "https://hashnode.com/posts/using-storybook-with-expo-router-v2-sdk-49-typescript/64b022fe0ba7115b2af1d9ce/comment/659e2bac67939dc421ce405e"
---

[Discussion](https://hashnode.com/posts/using-storybook-with-expo-router-v2-sdk-49-typescript/64b022fe0ba7115b2af1d9ce)

Comment [Using Storybook with Expo Router v2, SDK 49 & TypeScript](https://hashnode.com/posts/using-storybook-with-expo-router-v2-sdk-49-typescript/64b022fe0ba7115b2af1d9ce)

[Hayata Suenaga](https://hashnode.com/@Hayata)

[Jan 10, 2024](https://hashnode.com/posts/using-storybook-with-expo-router-v2-sdk-49-typescript/64b022fe0ba7115b2af1d9ce/comment/659e2bac67939dc421ce405e)

I really enjoyed the article, and it was very helpful in getting started with setting up Storybook in my Expo project.

Now, as I'm trying to create a production build, I have a new question. How can we ensure that the production build doesn't include Storybook code?

Switching the real and Storybook application conditionally inside the code doesn't prevent Metro from bundling Storybook code.

I'm currently exploring a solution to this issue, but if you have any suggestions, I would greatly appreciate it if you could share your thoughts.