Ruben Bridgewater 📍 Frankfurt

@NicoloRibaudo @WebReflection Node.js does not strip types from node_modules. That will hppefully prevent publishing TS directly

the only sad thing about Bun is that we're back to people publishing to npm .ts files making modules interoperability a mess 😥 we used to know better ... and I get some module might even use explicit Bun APIs but why even bother a transpiler in production? Please publish .js 🙏

Last day of the @nodejs Collaborator Summit, Dublin 2022

🙌 Error Cause logging coming to Node.js PR of @BridgeAR freshly merged! github.com/nodejs/node/pu… twitter.com/sebastienlorbe…

🌟 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): goo.gle/devtools-recor…

This event promises to be epic! js-poland.pl @codepo8 | @BridgeAR | @wa7son @matteocollina | @BenLesh | @nirkaufman | @jayphelps | @Michael_Hladky | @ShmuelaJ | @gerardsans | Chen Salomon | @MartaW_PL | @ManfredSteyer | @joe_sepi | @shai_reznik and meny more!

I'm speaking at #NodeCongress today. Join me nodecongress.com if you are interested in memory handling in #JS and #NodeJS!

I know some @nodejs folks have been waiting for this :)

@joe_sepi @mmarkini @matteocollina @bengl @jasnell I miss our karaoke sessions

@mmarkini @matteocollina @bengl @BridgeAR @jasnell Someone mentioned the idea of Zoom Karaoke. I dont know what this is, but I'm listening....

Node.js Interactive -> OpenJS World Node.js Collab Summit -> AMP Summit with a side of Node.js

Nobody working with "hot" code (code that needs to be fast) would be using array methods anyway. for loops FTW 🔥

I am looking forward to my talk at @jsPolandConf and to see some of you there

@wa7son You might want to inspect it as in: console.log(util.inspect(object, { showHidden: true, showProxy: true, customInspect: false, colors: true }))

Ok, JavaScript twitter. Tell me what happens in "???" The very act of accessing the property seems to create it?!?

@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.

@BridgeAR @nodejs It's doable when you're the author of the script. If you're a user and want to turn off some feature for the package bin, but not for the npm/npx that runs this package?

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

@ehosca @nodejs What else do you use to separate your applications configuration from your code?

@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.

@BridgeAR @openjsf @nodejs It’s totally fine but make the name of the environment variables less generic than “FORCE_COLOR”. E.g. “NODE_FORCE_COLOR”

@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.

@BridgeAR @nodejs If only a few would be allowed, would a whitelist do the trick? Not necessarily a good idea, brings other concerns.

@FerryColum @nodejs The example is only about deactivating / activating colors. Not about what colors might be used.

@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., npmjs.com/package/dotenv.

@BridgeAR @nodejs Doesn't mean it won't happen. Plenty of reason of doing those kind of "shouldn't be done" things. ie. easiest workaround, etc.

@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.

@BridgeAR @nodejs It would be totally confusing when node is the child process of node (ex.: npm run). How do you tell the "parent" one to use colors and the "child" one not to use it?