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

UI: Externalize react-syntax-highlighter from components #18127

Merged
merged 1 commit into from
May 3, 2022

Conversation

ndelangen
Copy link
Member

Issue: #18090

What I did

Externalize react-syntax-highlighter

I think in the future we'll have to migrate away from react-syntax-highlighter because of the bug described in the issue.

Possibly we could migrate to call Prism directly, or find some other alternative.

@nx-cloud
Copy link

nx-cloud bot commented May 3, 2022

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 43d873e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

@ndelangen ndelangen self-assigned this May 3, 2022
@ndelangen ndelangen requested a review from shilman May 3, 2022 13:28
Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@shilman shilman changed the title change the bundle of lib/components so react-syntax-highlighter isn't in it UI: Externalize react-syntax-highlighter from components May 3, 2022
@shilman shilman changed the title UI: Externalize react-syntax-highlighter from components UI: Externalize react-syntax-highlighter from components May 3, 2022
@shilman shilman merged commit dbc18f8 into next May 3, 2022
@shilman shilman deleted the norbert/sb-328-sb18090-code-block-displaying-object branch May 3, 2022 16:26
@zachbryant
Copy link

Heya, I got here after I encountered issues with Volar and @types/react-syntax-highlighter not playing well together. Are there any intentions in the future towards putting the types back in devDependencies?

@ndelangen
Copy link
Member Author

Yes, in 7.0 it will all be encapsulated fully!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants