You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you so much for your effort on scoped!
I'm a core member of the team Qiankun, we ran into the same need for style isolation and already have a working solution of our own. Recently, we came across your implementation on MDN, which our implementation is very similar to (you can find it here). Since it just makes more sense to use a library that already exists, we decided to replace ours with scoped and we would be happy to collaborate with you on any of the following:
Building an interface on top of the scoped project to make it more accessible and importable when used in other projects (This will be one of the biggest features in the Qiankun upcoming 3.0 release, more details here).
For sure. I wrote this code mostly in 2017 and it could use a bit of upgrading, although I don't think by that much.
There's a few major parts:
- the MutationObserver and friends which actually notice `<style>` being added/removed/modified on the page (some other polyfills didn't do this, they just did an initial pass)
- the XHR-based loader which deals with imports into scoped CSS
- complex regexps which rewrite nested CSS selectors (you don't always just want to add a prefix to make the polyfill work)
Maybe you want some or all of those.
Hi there👋,
First of all, thank you so much for your effort on
scoped
!I'm a core member of the team Qiankun, we ran into the same need for style isolation and already have a working solution of our own. Recently, we came across your implementation on MDN, which our implementation is very similar to (you can find it here). Since it just makes more sense to use a library that already exists, we decided to replace ours with
scoped
and we would be happy to collaborate with you on any of the following:If you are interested, please let us know, we are more than willing to provide a more detailed API proposal and to contribute PRs!
The text was updated successfully, but these errors were encountered: