Will Harney

```ts // `Class` appears unused, but by doing `Name extends keyof Class`, the result type preserves // the optional/required status of each prop. If we just do `Name extends PropertyKey`,...

> I wonder if this approach means we could restore support for experimental decorators. Turns out we can't, because of https://github.com/salesforce/lwc/issues/5087#issuecomment-2583214496. The LWC compiler required decorators to be preserved, and...

> This is an incredibly popular package; 12.8 million weekly downloads. There are also a load of packages within DT which depend on @types/tough-cookie, unfortunately the DT infra is not...

Sadly (but unsurprisingly), it turns out there are some differences. The biggest is that the `@types` package defines two namespaces that we don't use in the v5 release. The rest...

Ready to merge

If we're moving forward with sync mode, do we need to block more flavors of async operations?

Browsers (well, Chrome, at least) are perfectly happy to allow `autofocus="STRING"`. We should allow, but warn that it's not necessary.

It's probably more performant to not define things unnecessarily, but adding empty property descriptors would help avoid subtle foot-guns. In any case, running engine-server fixture tests with `NODE_ENV=production` currently has...

Thanks for reporting this issue! It looks like an issue with the resource loader module, not the LWC framework (this repo). To resolve your issue, I would recommend opening a...

Thanks for the suggestion! Can you elaborate more on the use case that you're trying to solve? What are you trying to do that cannot be accomplished with the current...