added next.js 14 support #576
Conversation
|
Co-authored-by: Marco Franssen <[email protected]>
|
Still no merge? |
|
Can we installed this versions? |
|
Please.... |
|
Unprofessional |
|
Please merge it already |
|
Is there any issue which needs to be fixed? what is holding up the merge. Happy to help if any. |
|
Been using Next.js 14 with Contentlayer for a while, no problem found. Surely this should be merged since package managers like NPM will throw an unmet peer dependencies error due to the incompatible peer dependency version. |
|
Please merge this, it will helps a lot of people |
|
Is contentlayer still actively maintained? I've been excited to add this to my Next.js project the last several weeks, but it seems like the last changes were several months ago in September. Wondering if I need to look into alternate CMS solutions? Happy to help in any way to get this PR merged. |
Apparently, the project is no longer funded and it seems no longer very active. I am hoping that perhaps someone else might be willing to take over, so that it still can be maintained. |
|
commenting to subscribe for updates |
|
Also commenting to subscribe for updates. (and thinking about forking the repo for now) |
|
On November 7th I messaged him directly on Discord to become a maintainer for the project or for him to approve of the PR. I don't think he even read the message. Maybe we should fork and publish it to NPM? |
|
just add the following to your package.json as a quick workaround "overrides": {
"next-contentlayer": {
"next": "$next"
}
}This will make contentlayer work on nextjs 14. tested ;) |
Maybe you might have better luck if you message him on Twitter: https://twitter.com/schickling |
|
up 🙏 |
|
Apparently funding has stopped for the project and Netlify owns it. The current work around is to add this snippet of code to your root package.json. I am using turbo repo so it has to be the root package.json and if you aren't using a monorepo then you simply need to add it to your single package.sjon file. |
|
@leerob cant you guys take over :(( |
|
I understood netlify took over the company @schickling is/was working for. They haven't allocated budget yet to continue the maintenance of contentlayer and therefore it is kind of dead. |
|
Hi folks, Please excuse the late message here and the lack of updates. As others have stated above, the past work on Contentlayer was sponsored by Stackbit which has since been acquired by Netlify who hasn't yet been resuming the sponsorship of the project (still TBD but it's taking a while). Why isn't this PR merged yet?Merging this PR alone most likely won't be enough. There needs to be a new release (with a non-trivial release process) incl. updating transitive dependencies which often cause other parts of Contentlayer to break. In case there is any other company who'd be willing to sponsor the work on Contentlayer, I'd be up for a chat. I'd be happy to continue the work on Contentlayer as I'm excited about it and had many plans for it - and it's sad for me personally to see it neglected like this. (As much as I'd like, I can't currently commit to working on Contentlayer in my spare time.) 💜 |
|
hello anyone can merge??? |
Please read the comment above, it won't be merged until someone sponsors this project. |
Fork it! Cant believe this project is standing still like this. I dont have the skills yet to take on a fork of this, but would support anyone who wanted to/could do it! |
|
This pull request 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. |
closes #575.
On November 7th I messaged him directly on Discord to become a maintainer for the project or for him to approve of the PR.
I don't think he even read the message.
Maybe we should fork and publish it to NPM?
