We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
main
0e40674e88f8429fbb136d032ae77be17f1bda9c
site.config.ts
yarn dev
expected:
experienced:
0191bcee9db04c3690b84062af8f12e2
The text was updated successfully, but these errors were encountered:
just fyi the searching will still not work. see my comment in the PR #619 (comment)
Sorry, something went wrong.
for people trying to make searching work, react-notion-x version 6.16.1 has the fix NotionX/react-notion-x@v6.16.0...v6.16.1#diff-730f034e11dd4199e0434acf6897a2b1cb0642641b160fd1c5be24753fda487eR552 but unfortunately it is not published to npm. latest on npm is 6.16.0 https://www.npmjs.com/package/react-notion-x I tried cloning react-notion-x and trying to build but ran into arm64 related issues of sharppackage.
sharp
I found an alternative https://github.com/ijjk/notion-blog but that also does not use official notion client https://www.npmjs.com/package/@notionhq/client I anticipate that notion-blog will have similar issues. I think it is best that we create our own nextjs application with notion's client
Successfully merging a pull request may close this issue.
Description
main
branch on commit0e40674e88f8429fbb136d032ae77be17f1bda9c
(the latest as of this date)site.config.ts
as specified in readmeyarn dev
expected:
experienced:
Notion Test Page ID
0191bcee9db04c3690b84062af8f12e2
The text was updated successfully, but these errors were encountered: