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
If so, then that means maintainers of other projects aren't using your package correctly then, and this may cause/allow them to then do so. Would first like to gain this understanding though.
The text was updated successfully, but these errors were encountered:
Thinking more now after my post, I think that the library is geared in general towards any environment that does currently support BigInt... would that be a more proper conclusion then?
I think that the library is geared in general towards any environment that does currently support BigInt... would that be a more proper conclusion then?
Hi @sindresorhus, this is more of a question for understanding than an issue.
I've encountered at least one other OSS project, https://github.com/nearform/graphql-hooks (specifically, the https://github.com/nearform/graphql-hooks/tree/master/packages/graphql-hooks-memcache package), that is using your
v2.0.0
of your package, but within bothnodejs
AND browser. This got me thinking towards the intent of this library - is it intended to be used only withinnodejs
?If so, then that means maintainers of other projects aren't using your package correctly then, and this may cause/allow them to then do so. Would first like to gain this understanding though.
The text was updated successfully, but these errors were encountered: