Jesse Jafa

Rather than this specific example, of `div` inside `p`, I would suggest that this needs to be worded something like `Invalid HTML may cause a hydration mismatch` I don't think...

With the current state of web3 I really think it would be detrimental to allow this kind of content in the Next.js repo.

@leerob Above framework can be used auto mine ETH blocks. As you certainly know that is disallowed from most hosts, including Vercel. With Next.js being primarily a web framework I...

> @silentlight could you clarify the intent of the example? @awareness481 looking at the code, it doesn't seem like it's set up for that, but I could be missing something....

This is "solved" if you add the `"use client"` directive to the top export (`src/components/index.ts` in this case).

According to this https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#supported-unsupported-features amplify supports only up to Next v11 . It seems like amplify is adding the `target` property to `next.config.js` which is not supported in v13.

@mattvh Would you be interested in an initial implementation and see if we/you can build from there? I am interested in contributing

I think an issue is that `get_iterator_inner` https://github.com/dudykr/stc/blob/8ea5b02590550cdd7d1e6cbf53a54bc719be99a2/crates/stc_ts_file_analyzer/src/analyzer/expr/array.rs#L605 is **never called**, which by running the conformance tests on the `microsoft/TypeScript` repo I figured should be called for this to be...

> I think it being `Tuple` is the correct behavior, but not sure. Maybe we should use `Widen` on the type. `Widen` will convert a `Tuple` to an `Array` if...

I think you're right that they should be widened, at least thats what I understood from stepping through the ts compiler, but I couldn't tell if it's because there is...