Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback for “Quickstart with Next.js” #139

Open
cdaringe opened this issue Nov 6, 2024 · 0 comments
Open

Feedback for “Quickstart with Next.js” #139

cdaringe opened this issue Nov 6, 2024 · 0 comments

Comments

@cdaringe
Copy link

cdaringe commented Nov 6, 2024

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 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant