Recent searches
Search options
Administered by:
?nodefine — a pattern to skip automatic Custom Element definitions
Zach Leatherman?nodefine — a pattern to skip Custom Element definitions—zachleat.com
More from 
Zach Leatherman 
@develwithoutacause@techhub.social@zachleat FYI the static `define` pattern you describe is a proposed community protocol.
https://github.com/webcomponents-cg/community-protocols/blob/main/proposals/on-demand-definitions.md
My hope is that tools and frameworks can use this knowledge to auto-generate the `.define()` call when using a custom element such that you don't need to worry about something like `?nodefine`.
GitHubcommunity-protocols/proposals/on-demand-definitions.md at main · webcomponents-cg/community-protocolsCross-component coordination protocols. Contribute to webcomponents-cg/community-protocols development by creating an account on GitHub.
@develwithoutacause ooh this is lovely — thank you! I’ll link it up from my post
@develwithoutacause @zachleat wow this is an awesome proposal! Here's hoping it really gets traction 