Skip to content
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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

AVGVSTVS96
Copy link
Owner

@AVGVSTVS96 AVGVSTVS96 commented Aug 5, 2024

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 the react-shiki: workspace*, despite the setting to include files outside of the root dir (playground) being enabled.

Copy link

vercel bot commented Aug 5, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-shiki ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 13, 2024 1:52am

Copy link

changeset-bot bot commented Aug 5, 2024

⚠️ No Changeset found

Latest commit: 936f41b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Owner Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AVGVSTVS96 and the rest of your teammates on Graphite Graphite

@AVGVSTVS96 AVGVSTVS96 changed the title Add react-shiki from npm Add react-shiki from npm for docs deployment Aug 5, 2024
@AVGVSTVS96 AVGVSTVS96 force-pushed the demoDeployment branch 2 times, most recently from 543fe24 to 317af61 Compare August 6, 2024 05:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant