process.config is not cloneable anymore in v16.x

@jasnell

v16.0.0 / process

#36902 made process.config immutable. That's fine in principle but the use of a Proxy breaks the following code:

v8.serialize(process.config) // Uncaught Error: #<Object> could not be cloned.

The properties themselves are proxies too so Object.fromEntries(Object.entries(process.config)) is not an easy workaround.

I suggest using Object.freeze() or Object.seal() instead.

We cannot intercept modifications on frozen or sealed objects and print warnings about that. That seems to be the key point of runtime deprecation.

The deprecation is here since v16.0.0. I think it should be fine to make it eol and lock the object in v19.0.0

process: make process.config read only

Navigation Menu