Code highliting with react-syntax-highlighter bug

remarkjs / react-markdown

Markdown component for React

https://remarkjs.github.io/react-markdown/

MIT License

13.29k stars 876 forks source link

Code highliting with react-syntax-highlighter bug #807

Closed Toavina23 closed 9 months ago

Toavina23 commented 10 months ago

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

9.0.1

Link to runnable example

No response

Steps to reproduce

I just copy pasted the example from readme for code syntax highlithing to my code

Expected behavior

should higlight the code correctly

Actual behavior

the code blocks are looking like in the image above instead of showing the code

Runtime

No response

Package manager

npm 8

OS

Windows

Build and bundle tools

No response

wooorm commented 10 months ago

You need to show code and versions and more. I cant look into your computer…

github-actions[bot] commented 10 months ago

Hi! Thanks for taking the time to contribute! This has been marked by a maintainer as needing a reproduction: It’s not yet clear whether this is a problem. Here are a couple tips:

Thoroughly document how to reproduce the problem, in steps or with code
Don’t link to your complete project: make the repro as tiny as possible, preferrably with only the problematic project in question
Make sure you’re on the latest versions of projects (and node/npm/yarn!)
The best issue report is a failing test proving it

Thanks, — bb

ChristianMurphy commented 10 months ago

@Toavina23 friendly ping 🔔 This still needs a way to reproduce the issue you are seeing.

Toavina23 commented 9 months ago

Hello,

Sorry for the late reply, after checking my code, the problem was that I was using two plugins that confilicted and gave this error.

ChristianMurphy commented 9 months ago

Thanks for following up @Toavina23! Glad you tracked down the cause. I'll close this ticket as it seems to be an external issue.

Though it could still be helpful to post which two plugins had a conflict and how you resolved it so future developers can benefit from your findings.

github-actions[bot] commented 9 months ago

Hi! This was closed. Team: If this was fixed, please add phase/solved. Otherwise, please add one of the no/* labels.

github-actions[bot] commented 9 months ago

Hi team! I don’t know what’s up as there’s no phase label. Please add one so I know where it’s at.

Thanks, — bb