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
Overriding global prototypes breaks node's module isolation and is generally considered bad practice in JavaScript.
Say you change the api slightly for _s, or discover a bug or improve performance or basically change anything at all about your library. Given that node allows you to have multiple simultaneous versions of the same package installed, which version of _s is actually used? It's determined at run-time (whichever version is loaded last, it could even change as the application runs). This is not how computer should work.
Please don't affect the global state in JavaScript, even if it seems very convenient.
The text was updated successfully, but these errors were encountered:
Overriding global prototypes breaks node's module isolation and is generally considered bad practice in JavaScript.
Say you change the api slightly for _s, or discover a bug or improve performance or basically change anything at all about your library. Given that node allows you to have multiple simultaneous versions of the same package installed, which version of _s is actually used? It's determined at run-time (whichever version is loaded last, it could even change as the application runs). This is not how computer should work.
Please don't affect the global state in JavaScript, even if it seems very convenient.
The text was updated successfully, but these errors were encountered: