Augustine Kim

Results 149 comments of Augustine Kim
trafficstars

I found a discussion in the nextjs repo regarding declarative shadow dom and posted a comment there. https://github.com/vercel/next.js/discussions/51717#discussioncomment-7626566 For now, I think we just won't be able to have custom...

Something we can do for now would be update the regex used in the plugin for the injection point to allow app folder structure, and document that custom elements to...

With https://github.com/lit/lit/pull/4293 merged, perhaps this can be rebased and revisited? I know @e111077 has tried this on MWC and had it work for its doc generation.

I'll close this issue as the original goal of this issue was completed a while back with `@lit-labs/react` exporting `ReactWebComponent` type as the type of the return value of `createComponent()`...

Closing as https://github.com/lit/lit/pull/3156 has been successfully merged and released

For those that might be subscribed to this issue, we have released [`@lit-labs/nextjs`](https://github.com/lit/lit/tree/main/packages/labs/nextjs) as a plugin for SSR-ing Lit components in a Next.js project. Here's a stackblitz example: https://stackblitz.com/edit/nextjs-lit-ssr?file=next.config.js,pages%2Findex.js Please...

@watife We added some more prop coordination with the `@lit-labs/react` package in this PR https://github.com/lit/lit/pull/3885. There's also a design doc explaining some of the goals and implementation decisions here https://github.com/lit/lit/blob/main/dev-docs/design/ssr-react.md

@watife See https://github.com/lit/lit/tree/main/packages/labs/nextjs#readme. There's an example project here https://github.com/lit/lit/tree/main/examples/nextjs. Please open a separate [discussion](https://github.com/lit/lit/discussions) if you're having trouble.

> In the nextjs example, I cannot import a library created with lit-labs/react like shoelace. To import it, based on above example, we will need the entire source of the...

This is an upstream issue in Next.js: https://github.com/vercel/next.js/issues/40769 There's a PR linked to the issue that should fix this. There probably isn't much more we can do on our end....