Worth noting that this is actually a no-op because the org-level setting is already readonly, but it doesn't hurt to be explicit
```suggestion - main ```
- fix: resolve circular references through custom revivers
Interesting note for the future: While I was working through this, I realized that without a WeakMap on the input payload, it's basically just impossible to have self-referential custom stuff, becaus…
This test already exists ```suggestion ```
```suggestion // If the payload is already hydrated, its recursion has already // terminated (e.g. a self-referential object cached itself before // following its own back-reference), so revive it di…
- Add a more straightforward method of opting dynamic explicit environment variables out of build-time validation
Yeah, should be `value === undefined`. Feel free to open a PR. If you're feeling ambitious, Rich was right about the function thing -- we all thought we'd implemented that already but clearly haven't…
```suggestion ```
- fix: uneval of a repeated empty Set or Map produces invalid JS
Sorry, we accidentally merged a couple of PRs that fixed some of this stuff before noticing you'd opened these. I'm closing the ones we've already fixed but will review the others shortly!
- Add a more straightforward method of opting dynamic explicit environment variables out of build-time validation
> we'll use this ugly hack that blows a hole in type safety I'm not sure what's particularly ugly about that; it's basically what we'd be exporting if we provided a helper for it. It just looks like …