Storybook: Add support for vanilla webcomponents without any third-party-support or -enhancement like Polymer

Created on 20 Aug 2019 · 5Comments · Source: storybookjs/storybook

I really appreciate the broad support for alot of frameworks and libraries, yet I sorely miss a version that is meant to be used for vanilla webcomponent development, without any supporting or enhancing libraries like Polymer. Just plain ESNext Code written for browsers that can run the code _as-is_ including full support for ES modules, private class properties and methods, in short: state-of-the-art web component development.

On our project so far we've been using Fabricator for the job - both as an asset building stack, and as a component showcasing environment. Especially for the latter we're less-than-happy with it.

Are you able to assist bring the feature to reality?
I probably cannot, because I'm yet to take a look behind the curtains of Storybook, but to the best of my abilities and knowledge, I'd be willing to help.

html feature request inactive

Source

franktopel

👍1

Most helpful comment

It looks like this is going to be a thing in 5.3.0

See v5.3.0-alpha.34 WebComponents Kitchen Sink

kylewelsby on 30 Oct 2019

🚀4

All 5 comments

cc @lonyele 😸

shilman on 20 Aug 2019

@franktopel Hi! Have you checked app/html which supports rendering plain html on Storybook. HTML guide If what you return is a plain html then it should work without a problem(btw if you want state-of-the-art, you can also setup Typescript with this app/html)

Just a side note, I know it can be little confusing but Polymer or other web-components related framework/compiler supports here at Storybook are kind of a wrapper that converts any framework specific code to pure web-components

I hope I answered your question?

lonyele on 20 Aug 2019

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!