This blog is going to highlight some of the reasons that LWC was also made into an open source project as part of the Salesforce journey. Here are a few key areas where we heard from the community directly:
Working in the open creates transparency
Build both on force.com and outside of Salesforce
Find solutions to problems outside of releases
Since all development environments are unique we have found that providing the underlying source can help many developers unblock themselves. A simple example we have heard multiple times is the ability to integrate into different testing and tooling workflows. We have been seeing the community open issues on our LWC repo and starting the helpful cycle of improving the LWC project.
Influence the direction of the roadmap
Influence the direction of Web Standards and Browsers!
The enterprise ecosystem is thriving and solving really hard, complex problems. With LWC, we want to take our developer community’s voice to web standards organizations such as TC39 and W3C, where Salesforce is a member. We believe that advancing the web is a community endeavor centered around trust, and we trust the community to examine and contribute to our code base, identifying areas where standards could be advanced further. This ability to influence the future of standards enhances the experience of web components for everyone.
We invite you to get started with Lightning Web Components (LWC) by visiting https://lwc.dev, and to tune into our developer evangelists Heather Dykstra and René Winkelmeyer, who are hosting a webinar Get Started with Lightning Web Components Open Source on August 8th, where they’ll demonstrate how the framework works, and how to use our open source tooling for it.
We are excited to see what you build!