-
Notifications
You must be signed in to change notification settings - Fork 175
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
WIP: Add entry points compatible with Next.js App Router #559
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
The
The build is about 5.5x slower in the CI than my local laptop. Which means the failing build would take about 2.4 minutes to complete if it wasn't running out of memory. :-p Previous builds took 21 seconds in the CI. |
767d00d
to
786a42e
Compare
786a42e
to
40df14b
Compare
🎉 Experimental release published 📦️ on npm! pnpm add next-drupal@0.0.0-pr.559.0c3c8cef yarn add next-drupal@0.0.0-pr.559.0c3c8cef npm i next-drupal@0.0.0-pr.559.0c3c8cef |
I'm getting an error when using the new experimental release:
I encountered this when using any functions, for example |
Same here |
Thanks for testing this PR release out. It was supposed to be a drop-in replacement for 1.6.0, but it's not working correctly. This is why we test! :D I'm not able to reproduce the jsona-related error. Instead I get a different error:
I know what is causing this error, so I'll fix that. I'm opening up a new PR with a different approach. |
BTW, with the new PR release, I am getting a |
This pull request is for: (mark with an "x")
examples/*
modules/next
packages/next-drupal
starters/basic-starter
starters/graphql-starter
GitHub Issue: #442
Describe your changes
Adds six new entry points so that developers can be more selective of which parts of the code base they import into their Server Components.