https://github.com/hashicorp/next-mdx-remote?tab=readme-ov-file#installation

This may help

Is this issue available to solve
Can I work on this issue
Also I want to ask is this repository under hackoctoberfest 2024

@RonakSurana-2001 Yes the repo is participating under hacktoberfest. You can work on it and open a PR.

@RonakSurana-2001 I am not sure, but maybe upgrading next.js version can fix this issue. it is worth a try.

@JeelRajodiya I added --turbo in package.json dev

And I am not seeing any Error.
I have also Added

in next.config.mjs as you suggested. but it is of no use as error is not coming.

https://github.com/hashicorp/next-mdx-remote?tab=readme-ov-file#installation

This may help

I have raised a PR you can see the change. #86

Hello @RonakSurana-2001 , please check your PR. I pushed some changes. Now you will be able to see this error.

I found these two issues somewhat relevant to ours.
vercel/turborepo#6094
vercel/next.js#44653

Hmm finding the solution

Think that issue is not with --turbo
I removed Providers from layout.tsx the error was gone

please reflect that in your PR

Think that issue is not with --turbo I removed Providers from layout.tsx the error was gone

@JeelRajodiya Can you please check #88 PR.

@JeelRajodiya is this issue still open?

can I work on it?

@pavanydg Let's give the issue to @iamridoydey, since he is new.

Please go ahead @iamridoydey.
Please note that, the issue might not even have any solution or the it is originated from the library itself. You can research online to figure out the solution of the issue.

Thanks @JeelRajodiya . I am looking at it. If I stuck then I will ask you for further help . Thanks for the support

Thanks @JeelRajodiya . I am looking at it. If I stuck then I will ask you for further help . Thanks for the support

You can also refer to the conversations in this issue. I have shared some of the related resources.

Thanks bro @JeelRajodiya

@JeelRajodiya After using
"next-dev": "next dev --turbo",
on the package.json . I got this error

Webpack is configured while Turbopack is not, which may cause problems.
[0] ⚠ See instructions if you need to configure Turbopack:
[0] https://nextjs.org/docs/app/api-reference/next-config-js/turbo

isn't it conflict with each other?

@iamridoydey I am not sure either : ) Maybe we need to configure turbopack itself, You can open a PR if you find any solution.

@JeelRajodiya still some issues. But i am looking at it

@iamridoydey I am not sure either : ) Maybe we need to configure turbopack itself, You can open a PR if you find any solution.

I am opening a pull request. Check it. It is working fine now.

@iamridoydey
You can try searching online to find any similar issues, (see my previous comment)

There might be two possible causes for the issue

1. Wrong trubopack configuration in our repository
2. Issue from next.js itself (if it is resolved from their side, it can be resolved by just upgrading next.js)

There might be any other cause as well, which I might be not aware of.

I upgrade nextjs ro 15.0.2 there turbopack work just fine. But get issues from other dependancy. So many dependancy are not working with current verions of the nextjs. They wants nextjs 14. There was the actual problem

@iamridoydey Can you please share a screenshot of the error. Which dependencies are causing the problem?

@JeelRajodiya I will but I am doing another project. Can you give me some time? Probably in the next day. By the way I am also working on a next js project where I use turbopack not experimental way. many dependancy need to update for this. So we can have a good discussion after I upload all of the issue. Can we?

@iamridoydey Yes, you can take your time.