[Sistent] Feat: JSX syntax highlighting on code pages of sistent

[lakshz]

Description

This PR fixes #5534

Before

After

• Light theme

• Dark Theme

Notes for Reviewers

Signed commits

• [x] Yes, I signed my commits.

[l5io]

🚀 Preview for commit 38b3d7436e946a3e7d636447ae49c01290342994 at: https://66409464683dc4aea8e762ba--layer5.netlify.app

[ritiksaxena124]

Hey @lakshz, let's discuss this on today's website meeting at 5:30 PM IST. I am adding this as an agenda item. Please Join https://meet.layer5.io/websites if you are available during the meet.

[Rexford74]

I'm dropping an approving review to this. I wonder if there are any contrary opinions @ritiksaxena124?.. 👀

[sudhanshutech]

@lakshz can you remove the Sistentthemeprovider wrapped from every component. It should be only mentioned at one place because it is wrapped globally and not on each comps. It can be mentioned at about or its guidance // @Rexford74 @nebula-aac your thoughts?

[leecalcote]

A merge conflict popped up, @lakshz

[leecalcote]

Checking back in. Looks like the merge conflict and response to feedback is needed, @lakshz

[lakshz]

When I try to commit after resolving merge conflicts, I see the below error:

Seems like, eslint dependency has migrated from using .eslintrc files, due to that the pre-commit is failing.

@leecalcote Should I continue with resolving the eslint issue in this PR?

[leecalcote]

@lakshz, PRs generally merge faster the smaller that they are....

[surajgjadhav]

When I try to commit after resolving merge conflicts, I see the below error:

Seems like, eslint dependency has migrated from using .eslintrc files, due to that the pre-commit is failing.

@leecalcote Should I continue with resolving the eslint issue in this PR?

HI @lakshz , This issue is resolved, Could you please take the latest pull and check again?