Drop usage of collections, it breaks globals
See original GitHub issueI landed here, because of a recursive dependency. The gist is that the mere requiring of the module collections
randomly breaks code in unrelated modules because it modifies globals. It is documented that this breaks things like crypto
from node core but there does not seem to be a fix coming: https://github.com/montagejs/collections/issues/162
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:15 (3 by maintainers)
Top Results From Across the Web
c++ - Global variables (again) - Stack Overflow
Global variables (again) · I just wanted to comment that I greatly share your point of view when it comes to the term...
Read more >Using variables | Postman Learning Center
Global variables enable you to access data between collections, requests, test scripts, and environments. Global variables are available ...
Read more >Memory management - JavaScript - MDN Web Docs
... JavaScript automatically allocates memory when objects are created and frees it when they are not used anymore (garbage collection).
Read more >Python Collections Module - GeeksforGeeks
The collection Module in Python provides different types of containers. A Container is an object that is used to store different objects and ......
Read more >GroupBy and Ungroup functions in Power Apps
This function returns a table, breaking into separate records any records that ... Use the DropColumns function to drop the group table.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just ran into an issue with
Array.prototype.find()
being overwritten bycollections/shim-array.js
as well.So - in reference to your last comment @kriskowal: ‘q-io@v2 depends on q@v2 and collections@v2, which does not have shims’ - why is q-io v2 not latest on npm?