This is a good way to learn nextjs:
https://nextjs.org/learn

Thanks, I already went through it, but from my point of view, it neither explains nor demonstrates the concepts well enough , i try to find good updated course or book

If you have finished the learn course, you have finished all the courses you need. Now you should be making actual projects to gain experience. Doing projects will also help you gain exposure to more advanced concepts and the process to understand and make use of such advanced concepts.

That's not how I feel, but thanks for the advice 👌

yea, It's definitive a thing of gaining experience at this point. Start by creation small projects like standard todo apps. Maybe get some experience with apis and libraries via a wether app and while developing these projects you will get more ideas what you can do 🙂

If you want to get more details and basics (absolute basics: no projects), then checkout [Codevolution](https://www.youtube.com/@Codevolution). He's very good in explaining and explains the basics even more.

He also done one for app router: https://www.youtube.com/watch?v=ZjAqacIC_3c&list=PLC3y8-rFHvwjOKd6gdf4QtV1uYNiQnruI&index=1

Or if you just want more basics: https://www.youtube.com/watch?v=N8YMl4Ezp4g&list=PLC3y8-rFHvwhuX4qGvFx-wPy_MEi6Jdp7

I hear that argument a lot, but in my case, I don't find it relevant because Next.js-specific objects won't be explained by small projects. That's why I took some courses that seems to extend the explanations provided in the documentation . Thanks for your ressources btw

Great video, but again, it does not explain the documentation. I already ran into this issue with the Prisma docs and had to read the source code to understand it. I hope to find someone who has done a thorough job of explaining the features of Next.js, but often this isn't the content highlighted by online resource platforms.I don't know if you guys are aware of such content.

yea, I guess it's what we make of it. Of course you can create a todo app with use client everywhere and then using localstorage to store everything. But you can also think in the other way of maybe storing data inside a database and make the todos only revalidate after changing something or whatever. So you decide how you want to solve the project 🙂

Many people (me included) think that the nextjs docs are pretty good. So you might also want to learn how to read docs?

Okay, so maybe you know where I can find an explanation of what 'missing' and 'has' mean in the matcher or 'nextfetchevent' before they are mentioned.

yea, you can read about both things here: https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher

Just to make it clear , I'm not criticizing the incredible work behind the documentation; I'm saying it's not suitable for my use case.

i read it twice or third "where has , missing and stuff are explain ?"

how as a beginner i can know what is "'next-router-prefetch' "

As far as I understand this its:
missing: if the incoming request is missing the (header) next-router-prefech execute the middleware.
And same for has: If th incoming request has the (header) next-router-prefetch execute the middleware

Yes, certainly, but it's not clearly stated, and as a beginner like me who isn't familiar with middlewares, I need to read explicit explanations to be sure of my interpretation

In summary, this documentation does not meet my needs. That why i need external explicit ressources 🙂

wdym by

external explicit ressources

?

Someone who explicitly details the documentation, for instance explaining how 'has' and 'missing' work and how the matcher is used by Nextjs to create routes, because even though the documentation does a great job summarizing and presenting Next.js features, it's not very precise as shown in this small example. As i do many mistake i need something very precise on each part of nextjs .I hope you understand that my need is not in any way a criticism of the work done, which seems to suit the majority of people

When I read this the first time it was pretty logical because of that:
I am in the matcher section. What does the matcher do? It checks specific conditions. If the condition is true the middleware will be executed. What kind of conditions can I add? Ah ok, some header stuff. It seems like I can execute the middleware when a specific header is there or not there. Ah ok got it. Sounds pretty simple 🙂

As i do many mistake ...

I don't know how you are a developer, but after some time you learn, that you can't do everything perfectly and that you can't create everything first try without mistakes. It's good to make mistakes

Last question before I go: do you know where I can find the definition of config in middleware.js (everything that can be specified within it)? Thank you so much for investing so much time; it's incredibly valuable for Next.js beginners 🤍

As far as I can see it's only the matcher right now

there is a link in the doc with kind of type/schema for config ? As you I only see 'matcher,' but it's not stated that it only contains 'matcher'

https://github.com/vercel/next.js/blob/b8bf2c84b91033058b1fdd5e4c9ea09c1f08857e/packages/next/src/build/analysis/get-page-static-info.ts#L37 ?

https://nextjs.org/docs/app/api-reference/file-conventions/middleware#config-object-optional finally

oh I like that. Thanks 👏

@Silky ant solved?