John-David Dalton

> Seems quite unlikely, but... is that reason enough to avoid it? Ya, dumping to a global is something to be avoided. I imagine if it was an issue Underscore...

OT: Is it possible to make [core-team](https://github.com/orgs/AmpersandJS/teams/core-team) & [community-leaders](https://github.com/orgs/AmpersandJS/teams/community-leaders) public?

> i don't see any way to change it. Why does it matter? It'd be rad if Ampersand core, & relevant teams that make decisions in core, were public. >...

Immutable `assign` is something I've heard more call for recently but is not on our roadmap at the moment. I'm not against adding an immutable `assign` and `merge` so bikeshedding...

The name `assign` aligns with `Object.assign`. So I see it as merge will attempt to merge values while assign/extend will assign values (overwriting previous values). As for naming, lodash has...

Yes the tests are in flux. Any PRs to help get them up and running would be appreciated :D

Closing as nothing actionable on our end I believe. Thanks ya'll for finding workarounds!

The issue is that if I mark them as deprecated they return an exit code 1 for CLI's and that would cause mass disruptions for folks.

Hi @arnaudbuchholz-sap! @nclavaud is correct. The per per-method packaged are discouraged and deprecated. If you find the prototype pollution or regexp dos security issues against them real for you, then...

~~It's a bun issue! I'll report it and link back ASAP.~~ Actually bun is more correct here. We want to side with bun here and respect `-0` if our APIs...