-
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
Add navigation entry point compatible with Next.js App Router #600
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
🎉 Experimental release published 📦️ on npm! pnpm add next-drupal@0.0.0-pr.600.128d03bc yarn add next-drupal@0.0.0-pr.600.128d03bc npm i next-drupal@0.0.0-pr.600.128d03bc |
Seeing the |
The |
d381a47
to
481b87c
Compare
481b87c
to
d9cba1f
Compare
d9cba1f
to
d196770
Compare
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
d196770
to
97c4156
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
This pull request is for:
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.Also switches from microbundle to tsup, a TypeScript-specific bundler that has built-in support for build-specific type definition files. And upgrades TypeScript to v5 from v4.