Will Harney

Thanks for reporting this issue, @Sdamodaram! I've managed to reproduce it, and it also looks like a regression we've introduced in v3. I will file a ticket internally to track...

Thanks for reporting this, @GerFres! While investigating this, I also noticed that if a user does not update the shipping method, they can make it all the way to submitting...

This is an issue with a Lightning Component, not the LWC framework (this repo). To resolve your issue, I would recommend opening a [Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/tagged/lightning-web-components) question or a [Salesforce...

This is a feature request for a Lightning base component, which is outside the scope of this repo (the LWC framework). You may consider submitting this feature request via [IdeaExchange](https://ideas.salesforce.com/s/),...

We currently use an internal tool for publishing releases. It does not support provenance. We may be migrating to a new tool at some point in the coming months. I...

The three failing tests are due to a regression fixed in #5640. If you update your PR then they should be resolved.

/nucleus ignore --reason "still broken"

To be more specific, it seems that reactivity only works when the prop is a valid identifier -- quoted `"reg"` is a string literal, and does not work. Similarly, `1337`...

Thanks for figuring out where the `undefined` is coming from! > Also, An actual error was thrown previously also, during other patches (props, attrs, etc...). It's just that now `patchDynamicEventListeners`...

Just sharing a [playground](https://stackblitz.com/edit/salesforce-lwc-vxndarcx?file=src%2Fmodules%2Fx%2Fapp%2Fapp.html) that did _not_ reproduce the error.