Creating a library agnostic approach to sustainable Web Component development

2019 is the year of the Web Component. The V1 specification stabilized and picked up a lot of adopters in 2018. Firefox, Safari, Chrome, and Opera all support them natively now and Edge recently announced hollowing itself out for Chromium. This both drove IE11/Edge users to other platforms but also means that future versions from Microsoft will support web components natively as well.

But who knows what they are let alone how to make them?

BoF structure:

• 5 min - Why the ELMS:LN core team has bought in hard on them and believes they are the future for everything
• Rest of the time discussion:
  • discussion of what libraries people are using,
  • have they heard of web components
  • what confusion can we dispell as a group / clear up issues people have had with them or FUD surrounding them
  • what do you wish components did
  • What awesome components exist or do you wish existed
  • What tooling are you using
• Have a group that can then go to lunch together and discuss these things in more detail
• Come back after lunch and go to the Coding rooms on floor 6

Coder room goals:

• Get everyone setup with what they need to develop, compile and publish web components
• yarn global add @wcfactory/cli
• help troubleshoot questions as a group working toward a common goal -- get a to-do list or hello-world or my-company-card published to npm and registered on webcomponents.org as a valid, meaningful component

@heymp and @btopro will help guide the discussion / help anyone get setup with things after lunch that wish to dig into code / tooling but have really needed a helping hand (it's complicated but we can all get there together!)