🌟 Introducing the new Recorder panel 🌟
You can now record, replay and measure user interactions with @ChromeDevTools.
See it in action - ordering coffee. ☕️
Learn more about this preview feature (available in Chrome Canary now): https://t.co/TGleZ2wo43
Want to know the Secrets of Memory Leaks? For the Second Time at @jsPolandConf Ruben Bridgewater @BridgeAR !
Topic: Demystifying Memory Leaks in JavaScript
Participants understand the Node.js memory handling and their shortcomings.
@wa7son You might want to inspect it as in:
console.log(util.inspect(object, { showHidden: true, showProxy: true, customInspect: false, colors: true }))
@subzey@nodejs It should mainly be the responsibility of the author to guarantee that everything works as expected. If a functionality relies upon specific options, make sure to set those while calling the function instead of relying upon the defaults.
To all Node.js users:
Should environment variables be used to override API default values?
E.g., FORCE_COLOR to activate or deactivate colors using `console.log()`.
Please RT for reach. This might have impact on Node.js itself.
@nodejs#NodeJS#JavaScript
@eaviles@openjsf@nodejs The variable name was already set by the ecosystem when Node.js incorporated it. Naming is always tricky and difficult to get right.
@Vadorequest@nodejs A whitelist is probably not sufficient but I'll give it a thought about passing through module names with the runtime flag that would activate such restricted mode.
@Vadorequest@nodejs I agree. I actually considered opening a PR to prohibit setting environment variables from node_modules. The issue is that this would clash with e.g., https://t.co/7GCRqQosga.
@subzey@nodejs Child processes inherit their environment variables by default but it's possible to define them independently while starting the child process. If you want to guarantee a specific behavior for something, please always explicitly define required options.