i cant think of a reason to include "use client"

[devlzcode]

its only been annoying that i have to make the decision of either using nuqs or nuqs/server especially when the usage seems to be ambiguous. when using it with react-router its especially annoying since loader and action are colocated with the component so do import both or one??

[franky47]

TL;DR: The 'nuqs/server' import is only useful when using Next.js app router, in all other cases you can import straight from 'nuqs'.

The main difference between the two imports is the presence of the "use client" directive in 'nuqs', which is not present in 'nuqs/server'.

In the Next.js app router (which is currently the only framework that cares about the distinction), shared code (like search params definitions, and creating loaders and serializers) can be done importing from 'nuqs/server', so the code can be bundled in either client or server bundles. The only imports needing the "use client" directive in Next.js app router are the useQueryState(s) hooks.

For any other framework, importing from either doesn't matter. I tend to import from 'nuqs/server' whenever the code I write may at any point be shared with a Next.js app router app (eg: shared libraries in a monorepo).

I'll try and make the docs more clear about this.