Normal plugin depending on a server-only one causes an error

[CernyMatej]

Normal plugin depending on a server-only one causes an error

[danielroe]

The error is to flag up to users who may be unaware. I think in your case handling it manually is right.

It's common, for example, to have a server plugin injecting something, e.g. $someVar, which is not accessible on the client, and for users to think this is a Nuxt bug.

I think specifying a hard dependency on another plugin means it's needed, and we can't just assume that the user has accounted for it not being available on the client side.

So I think we'll leave this as is, but please do feel free to circle back if you think there's a better solution (or better log message)! 🙏

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-q8ahjp (Open reproduction)

[danielroe]

I think this makes sense, as the dependency is unavailable on the client...

Why do you think:

I'm not sure whether it actually affects anything, but even the error message should probably not show up.

[CernyMatej]

It's a tricky situation. On one hand, it makes complete sense to show an error message when a dependency is not available on the client. However, in use cases like mine — where I want it to be a dependency on the server but not on the client — it might be misleading.

Maybe I'm thinking about it wrong…

I'm using the plugin to fetch some initial configuration on the server and store it in shared state using useState.

I removed the .server suffix from the dependency and added an early return when executed on the client to make the error message go away.