Hahaha that's where I stopped too.

This posts intention was not to conflict with his point. I used it as a hook and because the simple perfect function he was showing reminded me of the one I mentioned in the article.

And I agree with you on the second half :).

We tested for both, the "happy" and the negative path. But the Javascript unit tests are run without the framework in between. So our function was returning expected results when run in isolation. Only when running it with Next.js the function became async which led to this dilemma.

Yes you are right and after our learning we changed the code to not use `use server` anymore for this kind of operations.

The documentation and tooling definitely got better and I don't think that such a situation is possible with the latest versions.

I just hope that some people who are still running the specific Next.js version won't fall into this as we did.

Hey, author here :).

Thank you for your critique and you are right, I struggled with this chapter a lot.

I will read the link to get a better understanding of this type and update the section.

If I may ask, do you have more sources where I can read up on the history and current uses of unique besides the rustonomicon?

Thank you again for your engagement! It is very helpful to get these insights from people with more knowledge.