-
Notifications
You must be signed in to change notification settings - Fork 177
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
Add navigation entry point compatible with Next.js App Router #583
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
🎉 Experimental release published 📦️ on npm! pnpm add [email protected] yarn add [email protected] npm i [email protected] |
50d3cc0
to
2dc4bcf
Compare
6a71c78
to
2dc4bcf
Compare
Using
|
I've done some preliminary testing of |
I'm a bit concerned about commit 9d5d410 as its a bit of a hack to get separate type definition files for CommonJS and ESModule builds since I'm looking at tsup because it is a TypeScript-specific bundler that has built-in support for build-specific type definition files. |
For comparison of
And here's the build time from the GitHub Action for #600 (tsup):
tsup is more than 5x faster for building |
Fixes #442 BREAKING CHANGE: The useMenu() client hook has moved out of the main entry point and into its own entry point. Any import or require of that function needs to be updated: Old usage: ```js import { useMenu } from "next-drupal" ``` New usage: ```js import { useMenu } from "next-drupal/navigation" ```
Prevents "TypeError: Jsona is not a constructor" error
32dc5ae
to
5dc6e2d
Compare
Closing in favor of #600 |
This pull request is for: (mark with an "x")
packages/next-drupal
GitHub Issue: #442
Describe your changes
Moves the
use-menu
hook to a new entry point so that developers can import any of the other exports from the main entry point into their Server Components.An alternate build of this feature is at #600