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

Add support for Next 14+ => next-contentlayer #615

Closed
NBK-01 opened this issue Dec 21, 2023 · 13 comments
Closed

Add support for Next 14+ => next-contentlayer #615

NBK-01 opened this issue Dec 21, 2023 · 13 comments

Comments

@NBK-01
Copy link

NBK-01 commented Dec 21, 2023

Can not use or install the next-contentlayer package when using NextJS 14.

@NBK-01
Copy link
Author

NBK-01 commented Dec 21, 2023

there are only temporary solutions for npm, but shouldn't next-contentlayer have "next: latest" rather than 12 | 13

@ArmantG
Copy link

ArmantG commented Dec 23, 2023

Project isnt being maintained until further notice from Netlify... Not sure of the details, just saw some comments on other issues. Very irritated with this, doesnt take much effort for them to just update the deps.... Seems utterly useless from such a big project everyone is keen to use...

@Hidde-Heijnen
Copy link

Project isnt being maintained until further notice from Netlify... Not sure of the details, just saw some comments on other issues. Very irritated with this, doesnt take much effort for them to just update the deps.... Seems utterly useless from such a big project everyone is keen to use...

yeah @ArmantG it sucks tbh, any other solutions out there? Have been looking at @next/mdx + next-mdx-remote, but I honestly don't know where to go from here.

@ArmantG
Copy link

ArmantG commented Dec 29, 2023

Next-mdx-remote or apparently react-markdown will work. There are plenty of example next js blog repos available of you search github using next-remote-mdx. Contenlayer is just so easy and convenient to use compared to these though. Hoping it picks up steam again but yeah, I'm in the same boat. I'm actually looking at Astro + backend. Astro supports md out the box and mdx with a simple add on install. Backend I'm looking at whether bun + hono might be worth my time and how to combine hono and Astro into one project. But havent had the chance to really sit so far these holidays.

@Hidde-Heijnen
Copy link

Yeah, I know how to set everything up, it's more that I really liked contentlayer and don't want to implement an alternative. But I guess I will now for my portfolio, since their communication is also mediocre

@Seokhyeon315
Copy link

@ArmantG Yeah I was very heavy user of NextJS and contentlayer but recently, I am trying to move to Astro framework

@witcradg
Copy link

Is this still a problem with Netlify? Can Vercel handle this?

@Seokhyeon315
Copy link

Contentlayer team hasn't updated anything that compatible with NextJS 14.I think it has nothing to do with the Netlify or Vercel. We can still use contentlayer with NEXTJS13 version but many people want to use latest features of version 14 as well.

@ArmantG
Copy link

ArmantG commented Jan 23, 2024

Netlify bought the company who was sponsoring the project. The maintainer was receiving money from the sponsor which allowed him to spend more time on the project. Since the project isn't receiving funding and nobody knows whether Netlify will continue funding the project, its standing still... So yeah it does have to do with Netlify. It kinda works with Next 14 if you put some overrides in your package.json, but obviously long term it could become a problem if it isn't maintained to keep up with Next JS... Contentlayer basically only has one maintainer so yeah, doesn't seem like much will happen any time soon.
(I believe the information above is relatively accurate, but things could have changed since last I checked).

@AnweshGangula
Copy link

Contentlayer is probably not being maintained anymore as per this issue: #429

@AnweshGangula
Copy link

AnweshGangula commented Feb 12, 2024

a PR #638 is currently in open for this

@salvinoto
Copy link

So that's why it's showing version 13 on my 14 project....

Copy link

stale bot commented Jun 2, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale label Jun 2, 2024
@stale stale bot closed this as completed Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants