-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StoryDecorator and RenderFunction need to be exported. #8160
Comments
Possibly related: #8121 |
You were using https://www.npmjs.com/package/@types/storybook__react before? You should now get types without it, so there should be no need to import RenderFunction or StoryDecorator anymore. |
I was, but I've removed |
Please remove I'd recommend migrating to the docs addon, which has types! |
Thanks, @ndelangen. I tried removing Migrating to the docs addon is on the cards (it looks awesome!), but I was hoping to keep things working as I'm migrating. |
@rakeshpai The viewport addon doesn't need any types. It's a register only addon. Previously users would import a The addon info is unofficially deprecated. We will not add types to it. You could also take ownership of the |
Sorry, deleted my last comment, it was incorrect. I'll update this thread with my latest findings. |
Closing this issue since the specifics above have been resolved by removing the However, this hasn't been a smooth migration. I couldn't get I'll revisit the migration once 5.2 support for TS is more solid. Cheers! |
@rakeshpai we'll try to resolve the addon-docs typescript support soon in 5.3! you should also just be able to disable source code in docs for now as a workaround? |
@rakeshpai , (scratch that, nevermind) |
## <small>2.0.3 (2019-10-13)</small> * fix: remove storybook_addon-info base on storybookjs/storybook#8160 ([ee50893](ee50893))
Migrating to 5.2.x has caused build errors in my TS project:
It looks like
StoryDecorator
andRenderFunction
need to be exported from@storybook/react
.Expected behavior
Addons with TS should Just Work.
The text was updated successfully, but these errors were encountered: