-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
refactor: website components #8600
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
"minisearch": "^5.0.0", | ||
"next": "^12.2.5", | ||
"next-mdx-remote": "^4.1.0", | ||
"next-progress": "^2.2.0", |
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.
nextjs-progressbar is a good alternative with 30x more downloads
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.
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.
Theres actually a few differences between the 2 packages, one would be allowing full custom css, which nextjs-progressbar
doesn't. Plus its wrapped in a memo
, which nextjs-progressbar
is not.
"@microsoft/api-extractor-model": "7.24.0", | ||
"@microsoft/tsdoc": "0.14.1", | ||
"@vscode/codicons": "^0.0.32", | ||
"ariakit": "^2.0.0-next.41", |
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.
I recommend setting it to the exact version (without ^
) while it's in alpha so that you don't get breaking changes by mistake.
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification: