I'm excited to try these out!

Great minds, I guess... 😂

wc-toolkit.com

You will likely still end up with layout shifts, right?

The autocomplete issue has been patched. 🤘

Check it out here:
wc-toolkit.com/integrations...

3. Again, these are global, so adding `--width: 50% !important;` on a parent element will cascade and can really mess up the styles in the child elements - espically since custom css properties traverse the shadow DOM.

2. These APIs are global in that they can be set anywhere, so developer tooling and types declare these globally (and usually only once per name), so there's either a million `--with` properties in your editor's autocomplete or one with an inaccurate description and expected type.

1. This improves the user experience by making it easier to identify the correct API for making a change (whether in a global theme file or in some local or inline CSS).

Yeah, I tried that for a while, but I think the term "web components" has more brand identity than "custom elements".

I still try to use "custom elements" when I'm specifically talking about them, since I think that is an important distinction from JS framework components in some contexts.

Wait, seriously???

Would the default value accessor help here?
angular.dev/api/forms/De...

Here's a newer article from them.
ionic.io/blog/stencil...

Where did you get that @stenciljs.com is abandoned?

"Most importantly, Ionic’s open source software, including Ionic Framework and Capacitor, will remain free and open source. These will continue to be maintained and improved since they form a significant portion of the OutSystems mobile stack."

Sorry, a quick clarification point. It's a shell function, not a daemon, so it's not constantly running, but runs every time the terminal starts up to initialize the right version of node.

Correct. It runs when node runs.

Yes and no. At work we have multiple projects that each use a different version of node. The nice thing is that you can have a `.nvmrc` to ensure that project always runs on a consistent version.

nvm also runs every time you open a terminal and can slow down the performance.

According to my search engine:
"Fnm is solely focused on managing Node.js versions, while Volta manages the Node.js version and the associated tools like npm or yarn, making it a more comprehensive tool for JavaScript project toolchain management"

Speed