Augustine Kim

I'm not sure if this is how the typescript rollup plugin works but if you're already doing a typescript pass, can't you just keep experimental decorators true and let typescript...

So properties that hold context provided values with `@consume()` are not considered reactive properties so are not include in the `changed` properties of life cycles. A workaround if you want...

Using the controller directly as shown in the original issue workaround seems like a lot when it could just be ```ts @consume({ context, subscribe: true, callback: () => { console.log('The...

@filimon-danopoulos-stratsys what do you think about adding the `@state()` decorator along side the `@consume()` decorated field? This allows you to put all element level change detection in one place, within...

@keisha-rw this issue might be related https://github.com/lit/lit/issues/3845#issuecomment-1535531250 I'm not sure why nextjs sometimes fails to use the module with the correct condition but could answer why you're seeing mix of...

Using `@lit-labs/ssr-react` directly will work for situations where `React.createElement()` is used to create custom elements. You'd also need to set the [`jsxImportSource`](https://www.typescriptlang.org/tsconfig#jsxImportSource) to `@lit-labs/ssr-react` to handle runtime jsx, but I...

I don't think #4575 would fix this particular problem as it doesn't change anything about how user code is imported. When you say occasionally, is it the same app that...

Thanks for the additional info! The deletion of `node_modules` and `package-lock.json` was making me think it might be multiple copies of Lit within `node_modules`, but if `npm ls` shows everything...

@keisha-rw sorry for the delay. The Next 14 support and fix to those errors have now been released. I don't think it would do anything for the dev/prod mixup, but...

Good find! Thanks for the update. Hope that fixes it!