Unmaintained? New maintainers?

[karlhorky]

Hi @dstaley and @brkalow (since you seem like last active maintainers here)

First of all, thanks for next-mdx-remote - it is a great project and idea, and would be amazing to have this become a maintained library again!

There are a few areas where the maintenance of the library is currently lacking:

1. Broken types for modern TS module resolution: Fix file paths for modern module resolutions #377
2. MDX v3 (this causes confusing incompatibilities with using this library along with other modern plugin packages): feat: upgrade to latest version of mdx-js #433 by @DavieReid and mdx3 #425 by @hipstersmoothie
3. (other updates of dependencies would also be great)
4. CI is currently failing in main branch
5. (other issues and PRs)

There has not been much activity here lately. This leads me to a few questions, in terms of a path forward:

A) Will the last active maintainers @dstaley and @brkalow return to this project?
B) Is there anyone (outside of the last active maintainers) from HashiCorp which will actively maintain this project?
C) Should maintenance access be given to someone in the community?
D) Should the project be transferred to another organization or singular person?
E) Should the project be marked as "Unmaintained" with a large message in the readme and the repo archived?

CCs:

• From the Next.js / Vercel side: @jescalan
• From the HashiCorp JavaScript maintainer side: @DhariniJeeva @ZedLi @cameronperera @lisbet-alvarez @dvonanderson
• From the MDX / Unified side: @wooorm

[karlhorky]

Useful Forked Packages

Some useful forked (scoped) npm packages:

1. next-mdx-remote with MDX v3 (PR #433) from @DavieReid https://www.npmjs.com/package/@daviereid/next-mdx-remote
2. next-mdx-remote with MDX v3 (PR #425) from @hipstersmoothie https://www.npmjs.com/package/@alisowski/next-mdx-remote

[talatkuyuk]

I am on the way to release forked next-mdx-remote (actually It stopped being forked and became a brand new package after changes I made), fully re-written as inline with @mdx-js/mdx version 3 supporting imports and exports (except imports on pages directory), internally error handling, fully well-written type system and solving all issues, I fixed all of them, but requires breaking changes.

I've almost finished, working on writing tests, documentation and migration guide, github actions integrations, and on a sample website.

I tested it works perfect on both nextjs v13.5.6 and 14.1.0 and both app and pages directory.

[dstaley]

@karlhorky Thank you so much for asking these questions and summarizing the big opportunities for this library. I've started a discussion that outlines HashiCorp's plans for the near future for next-mdx-remote, and we can continue the conversation there. Thanks again!

[karlhorky]

@dstaley thanks for the reply and the detailed plan forward 🙌 I'm optimistic about the future of the library