-
-
Notifications
You must be signed in to change notification settings - Fork 393
feat: add waku framework provider #2132
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
Conversation
|
@himself65 is attempting to deploy a commit to the fumadocs Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
it's okay now |
thanks for the PR! Let me know when it's ready for review |
I think it's ready now. But I think we can hold this until the new waku version in the next weeks. there're some API changes |
import type { UserConfig } from 'vite'; | ||
|
||
export default defineConfig({ | ||
unstable_viteConfigs: { |
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.
it will be viteConfigs
in the next version
if it's just the examples needed to change, I think we can add the adapter first |
Thanks for contributing! |
/cc @dai-shi
limitation:
doesn't supportsorry this is another issue[...slugs]
related to Feature Request: Allow/[...catchAll]
routes to handle/
(index) routes wakujs/waku#1518