Anna Henningsen

> If the original request, the ability to mark a Buffer as read-only (or at least get a read-only slice of it), can be implemented by nodejs without requiring getting...

> which likely has a bigger interest in things like this for putting values into ROM as much as possible unlike most desktop runtimes Fwiw, I don’t think that’s the...

@mikeal Well, the reason that doing this inside of Node.js core is tricky is that we *have* switched `Buffer` to being based the language-provided feature, rather than keeping our own....

@ad-m I think that would require quite a bit of porting work, but if somebody’s up for that, why not.

@targos It definitely does :) I’ve been meaning to take a look at it and just see if this breaks something for us. But at a glance, from our/my perspective...

Just fyi, you can pass these options through an environment variable: `NODE_OPTIONS=-r a.js -r b.js`… does that help you?

Thinking one step further, I think if we were to implement something like this, it should be a file that lists generic options, not just requires; e.g. `node --options-file=foo` where...

Hey @Gowee – Thanks for the report! You are right as to what causes this, and we are aware of this pain point. We are currently in the design phase...

@Gowee Up to you! The alternative would be us commenting here to let you know once there’s an internal ticket to follow up on.

To clarify, `LoadEnvironment()` is only expected to be called once, and calling it multiple times may lead to surprising behavior of Node.js. We probably should be clearer about that. If...