Clarify status or archive?

[mrienstra]

It appears that this repo is not actively being developed. I'm basing this on:

1. General lack of recent activity

2. Remark plugins are not working #41 (comment) says:

   remark plugins need to be remark 13 compatible. [..] The next major release will support remark 14

3. [WIP] Next Major Release #39 hasn't received commits since Aug 25, 2021

Probably "archiving" this repo would be a bit much, likely work will pick up again at some point, but perhaps it would be helpful to at least add a notice near the top of the README.md about the current limitations, namely the lack of support for remark 14.

remark 14.0.0 was released Aug 3, 2021. remark 13.0.0 was released Oct 14, 2020, and has not received any updates since then (the following release was 14.0.0).

Along the same lines, it would be great to add a "When should I use this?" section like rehype-react and react-markdown, to help steer people to the best option for their needs.

Willing to submit a PR if that would be helpful.

PS: Hope the above doesn't seem unkind in any way, remarkjs contributors are doing and have done awesome work, which I very much appreciate. <3

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

[ChristianMurphy]

Welcome @mrienstra! 👋
Original author of this library and unified/remark maintainer here.
There's a lot going on in the community in the moment.
Upgrading this library continues to be of interest to me, processing incoming issues and discussions (including this one) is the top priority as part of the maintainer team is traveling right now, once things slow down redot and then react-markdown both will receive upgrades.
I would object both to archiving or adding a deprecation notice at the top.

remark 14.0.0 was released Aug 3, 2021. remark 13.0.0 was released Oct 14, 2020, and has not received any updates since then (the following release was 14.0.0).

When the upgrade happens it will likely go directly to remark 15, which is currently in the works, and also a higher priority.

I would be open to a PR expanding the install section to include notes on supported node version and remark versions. If you're interested in opening a PR @mrienstra
(reference https://github.com/remarkjs/react-markdown#install)

it would be great to add a "When should I use this?" section like rehype-react and react-markdown, to help steer people to the best option for their needs.

This would be a great add, feel free to open a PR @mrienstra .
The main benefits of this over say react-markdown are support for server side rendering, deeper support for rehype and rehype-react and for async plugins.
The trade off being, some may find the react-markdown component system more intuitive than the system here.

[punkpeye]

Remark v15 is out. Any chance on seeing updates here?

[punkpeye]

Hopefully useful to others https://glama.ai/blog/2024-10-21-rendering-markdown-in-react

[inad9300]

@ChristianMurphy Could you offer us an update on this?

I'm new to remark, and arrived here through a link in react-markdown which describes react-remark as a modern hooks based alternative. It seems simpler and just what I need, but lacking all context about its development, and seeing as it relies on very old versions of some dependencies, I worry about encountering major bugs and/or security vulnerabilities. Could you say something to this effect? It would really help me in taking a more informed decision.

Additionally, do you expect big breaking changes on subsequent versions of react-remark?

Thank you.

[remcohaszing]

I recommend you try react-markdown. It’s up-to-date and supports async plugins now.

[ChristianMurphy]

With react-markdown having hooks now as well as having rehype plugin support has resolved a lot of the pain points that this plugin was created to resolve.
The last difference is rending with rehype-react vs a custom renderer, I'm not sure if that's worth having a different package for.
With where react-markdown is at now, I'd be open to archiving this project.