You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently transitioned from two other hook libraries to this one, primarily due to its claim of being "server safe":
To my surprise, after implementation, I encountered an error in a Next.js application. This was unexpected, especially since other popular React libraries' "useLocalStorage" hooks do not exhibit this issue.
Moreover, the potential for this library to break in a server environment unless wrapped appropriately is not documented in the respective hooks.
Until this issue is addressed (it's been known about for 2 years), I kindly request that the "server safe" tagline be reconsidered? The number of existing issues related to this problem suggests a need to reassess the server safety claim. If a method requires undocumented wrapping to function correctly, it cannot truly be deemed server safe.
I've seen all the hacks and workarounds but it would just be more kind to state that up front so that people can make a more informed choice if they don't wish to use those.
The text was updated successfully, but these errors were encountered:
I recently transitioned from two other hook libraries to this one, primarily due to its claim of being "server safe":
To my surprise, after implementation, I encountered an error in a Next.js application. This was unexpected, especially since other popular React libraries' "useLocalStorage" hooks do not exhibit this issue.
Moreover, the potential for this library to break in a server environment unless wrapped appropriately is not documented in the respective hooks.
Until this issue is addressed (it's been known about for 2 years), I kindly request that the "server safe" tagline be reconsidered? The number of existing issues related to this problem suggests a need to reassess the server safety claim. If a method requires undocumented wrapping to function correctly, it cannot truly be deemed server safe.
I've seen all the hacks and workarounds but it would just be more kind to state that up front so that people can make a more informed choice if they don't wish to use those.
The text was updated successfully, but these errors were encountered: