-
Notifications
You must be signed in to change notification settings - Fork 522
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
Nextjs example #2068
Nextjs example #2068
Conversation
Ran npm init next-app nextjs-blog --example https://github.com/vercel/next-learn-starter/tree/master/data-fetching-starter
Fails with ./styles/global.css Global CSS cannot be imported from files other than your Custom <App>. Please move all global CSS imports to pages/_app.js. Read more: https://err.sh/next.js/css-global Location: pages/_app.js See bazel-contrib#2066
This Pull Request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs in two weeks. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs! |
Hi @alexeagle, just wanted to check-in. Did you have any luck with Bazel vs. Next.js? :) Would you happen to know how to overcome the issues blocking this PR? |
Any updates on this? I think Next.js example would be highly valuable |
So far it just hasn't been either funded by a company that needs it, or a fun hobby for someone in their spare time. Would love to work on this if some company needs it |
Makes sense. What do you think is the estimated effort? (a couple days, weeks?) |
Hard to say, I don't think we even identified all the issues. Depends what other assumptions are broken by next tooling. ts_project took me about two weeks I think. |
Btw the implementation with auto-generated Do you think this is a bug in the |
This Pull Request has been automatically marked as stale because it has not had any activity for 90 days. It will be closed if no further activity occurs in two weeks. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs! |
This PR was automatically closed because it went two weeks without a reply since it was labeled "Can Close?" |
No description provided.