You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next.js use the app-router (putting pages in <src>/app/pages/foo/page.tsx to host the /foo page), but it's unclear how to use that static page inside of my content script.
That is, I want to map the next.js /foo page to my foo content script, as opposed to just any old react component. Using the page model rather than any given component affords some value (styles, static data prep, etc).
The key idea is that Plasmo is your extension's entry point, and Next.js is your web application's entry point, allowing you to reuse your component across your codebase with minor adjustments.
Next is rather opinionated about pages. Is it feasible to marry the two entrypoints at dev-time & post build?
The text was updated successfully, but these errors were encountered:
Problem
Next.js use the app-router (putting pages in
<src>/app/pages/foo/page.tsx
to host the/foo
page), but it's unclear how to use that static page inside of my content script.That is, I want to map the next.js
/foo
page to myfoo
content script, as opposed to just any old react component. Using the page model rather than any given component affords some value (styles, static data prep, etc).Next is rather opinionated about pages. Is it feasible to marry the two entrypoints at dev-time & post build?
The text was updated successfully, but these errors were encountered: