Open Web Components retweeted
Ever reused a UI component and spent hours guessing how it works? With Custom Elements Manifest, your components come with contracts: typed props, events, slots & CSS vars—great for docs, IDEs & storybooks.
Lucien Immink shows how: javapro.io/2025/09/04/design…
@openwc #WebComponents
Does anyone know someone from npm/github/microsoft?
We really would like to get a hold on the unused `owc` npm namespace - but we are not getting any replay since February 😅
We opened "npm Name Disputes submission #2569951"
any ideas/hints?
Apple is about to break all PWAs in the EU under the guise of malicious compliance.
Please consider taking 10 seconds out of your day to sign this letter.
Open Web Components retweeted
I guess I'm officially announcing Component Odyssey:
component-odyssey.com/articl…
It's a course to teach developers how to build component libraries with minimal tech. CO focuses on web components, so your components will work anywhere.
Open Web Components retweeted
The Custom Elements Language Server 1.0.0 release is here!
Get it now!
VSCode: marketplace.visualstudio.com…
Neovim: Follow Instructions at github.com/Matsuuu/custom-el… (might need a couple of days for lib authors to update deps).
IntelliJ: Version 1.1.0 will ship with IntelliJ Support
Open Web Components retweeted
🚀 It’s Lit Launch Day, and we’re kicking the day off with a livestream going over all the things to get excited about with Lit 3.0!
Join us imminently, at 10 am PDT: youtube.com/live/ri9FEl_hRTc
Open Web Components retweeted
Custom Elements Language Server Alpha Release is out! Go check it out!
github.com/Matsuuu/custom-el…
youtube.com/watch?v=nfZqaGSB…
Open Web Components retweeted
Interested in Web Components? Check out my latest blog. link.medium.com/jZXuvidMvyb This is a re-publication & expansion of a section from a prior post. Since then, I discovered more erroneous info I wanted to correct. I'll continue to update this new article going forward.
Open Web Components retweeted
On process.env, bare module specifiers, import maps and package exports
dev.to/thepassle/the-javascr…
Open Web Components retweeted
#WebComponentsAdvent Day 10: Codelabs.
If you are new to Web Components and don't know where to start, today's update is for you! Check out codelabs: detailed step by step tutorials created by @buildWithLit, @ChromiumDev and @OpenWc teams.
webcomponents.today/codelabs…
Open Web Components retweeted
Look at that, @OpenWc just shipped some "spread" directives for @buildWithLit: github.com/open-wc/open-wc/b… There are A LOT of considerations to keep in mind when leveraging them: open-wc.org/docs/development… but, otherwise; glhf!
Open Web Components retweeted
🙌 THIS THURSDAY at 9:30AM PST: Join our first Lit and Friends Community Call!
Connect with members of the Lit team to talk about topics like #webcomponent standards, tooling such as Open WC, and more.
More info here ⬇ goo.gle/3Q3GqRN
Open Web Components retweeted
“I believe Web Components are one of the most exciting new technologies on the web platform today” @davatron5000
See why Dave is so excited about Web Components in his new course!
frontendmasters.com/courses/…
Open Web Components retweeted
I've heard good things about @OpenWc, will look into this more! Thanks for the tip!
Open Web Components retweeted
🗣 ICYMI: we've got two new series on YouTube!
Head on over to the Lit YouTube channel to get started with #webcomponents and subscribe to catch all the episodes for:
📺 Lit University
📺 Build It with Lit
Subscribe here ➡️ goo.gle/3saDCaY
LITX001_v2 (1).mp4
Open Web Components retweeted
Did a little writeup of my SSRed custom elements experiments here:
dev.to/thepassle/server-side…
Server side rendering vanilla custom elements in
@astrodotbuild
Open Web Components retweeted
For anyone listening to #developingDesignSystems, here's the link to the CEM Analyzer:
website: custom-elements-manifest.ope…
npm: npmjs.com/package/@custom-el…
Version 2.1.1 of `@open-wc/scoped-elements` is out 🎉
With it, we no longer automatically load a polyfill for a scoped registry.
Which results in
⬇️ smaller size
👼 fewer errors when integrating components in pages
As long as you are not requiring scoping no change is needed
If you need scoping and you are already using `@open-wc/scoped-elements` then loading the polyfill for the scoped registry will enable it.
And if you are imperatively creating elements then you should use the `createScopedElement` method.
For more details please see the release blog post
open-wc.org/blog/scoped-elem…

















