-
Notifications
You must be signed in to change notification settings - Fork 1
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 react-shiki from npm for docs deployment #4
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
543fe24
to
d230197
Compare
543fe24
to
317af61
Compare
317af61
to
7e5a56f
Compare
7e5a56f
to
2bf3ba4
Compare
2bf3ba4
to
e1fea72
Compare
e1fea72
to
e2a3fbf
Compare
e2a3fbf
to
62a4808
Compare
62a4808
to
936f41b
Compare
936f41b
to
3751145
Compare
3751145
to
d7546fc
Compare
d7546fc
to
b7b60f7
Compare
b7b60f7
to
d699ebb
Compare
d699ebb
to
f7b625d
Compare
This branch is maintained as the production deployment branch.
This branch imports the
react-shiki
package from NPM instead of using the package from the monorepo workspace.Vercel was unable to resolve
react-shiki
when using thereact-shiki: workspace*
, despite the setting to include files outside of the root dir (playground) being enabled.