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
Cover Salesforce "Lightning Web Components" #479
Comments
@rtm we will send a PR at some point in the future, but this repo does not have any framework that is not yet open sourced. If you are interested, I can add you to a couple of repos where you can try our experimental APIs. There are two folds to the interop with WC: I suspect that you have played around with Lightning Web Components inside the Salesforce's Lightning Platform, which has a lot more restrictions in place (due to Locker Service). If you want to try LWC in stand alone mode, just like any framework tested by this repo, just let me know, and I can add you to a couple of repos, maybe you will see the difference. As for your last statement, I don't think custom-elements-everywhere charter is to shame people or projects, it is to make them better, to help them be more interoperable, and that takes time and effort. For LWC, it is very very early on. |
@caridy Thanks for your response. I have played with LWC's outside of the Salesforce environment using the |
Ah, that explains! jest uses jsdom, which does not support web components API atm (we have multiple PRs open for jsdom to get this done). Since this is not the right place to follow up. I just sent you an invitation to a private repo, we can continue the discussion there. |
Looks like y'all have got things sorted so I'm going to close this issue if that's ok. |
Just as a heads up a formal PR has been opened in JSDOM to land WC support: jsdom/jsdom#2548 |
It would be great to cover Saleforce "Lightning Web Components", which are claimed to be based on web standards but in practice completely fail all interoperability criteria, if for no other reason than to shame Salesforce.
The text was updated successfully, but these errors were encountered: