Web Components

Hey friends!

If you're looking for a way to contribute to storybook's codebase, i might have a few small-ish tasks most people should be able to pick up!

We're in the process of migrating away from having custom scripts to prepare out packages for publishing to npm.
We've used babel and tsc to generate a modern, esm, and cjs output (in different directories.

We've picked a new

It's important, I think, if the goal is to communicate that this can replace React in more ways than function.

I have an podcast with episode uploaded to Mixcloud. I also have my music uploaded to Soundcloud. I'd like to see Mixcloud and Soundcloud added as providers with Vime.js

Also I endorse the feature request for playlist.

I plan to use this with an Svelte app.

The semantic dom diff plugin uses some global variables like __mocha_context__ and __snapshot__ which are only available in a karma mocha context. When it's user in other test runners, or karma without mocha, it crashes with an unhelpful message.

We should check for these variables, and throw a helpful error to the user that explains this plugin can only be used in Karma.

We have some code that looks like: if (rule instanceof CSSMediaRule) { which fails in happy-dom - I'm assuming this global needs to be defined?

All of the various Stylable directives should warn the user when receiving no arguments and at least 1 is expected.

Current status:

at-rules

• - @st-import
• - @st-scope
• - @custom-selector

rules

• - :global()
• - pseudo-states parameters (fixed)
  • [x]

The default data includes dfua16 links. These need to be updated to be relative or part of the compilation process.

and ensure that all libs are importable via the following browser ESM code.

import('//unpkg.com/lume?module').then(console.log)
import('//cdn.skypack.dev/lume').then(console.log)
import('//jspm.dev/lume').then(console.log)

At the moment they all fail with network errors for various reasons, namely some dependencies aren't in ESM format.