redyetidev

> since it is mostly abused by encouraging tests to be non-deterministic and non-predictable (in the majority of cases i've seen). such features are often used to hide flakiness instead...

@aduh95 I've implemented a basic syntax highlighter (I haven't decided on colors, right now it's all `inspect.colors.special` (unless `inspect.styles.X` exists)

The ReGexes used are inspired from a variety of sources, so I need to condense them a bit

[re-opened due to merge conflicts]

IIUC, you mean a similar function to `require.resolve`, where the user can supply [conditions](https://nodejs.org/api/packages.html#community-conditions-definitions) (maybe also [runtime keys](https://runtime-keys.proposal.wintercg.org/)) Said function would be used like: ```js resolve("my_module", { conditions: ["default"], entryPoint:...

@nodejs/loaders *Hypothetically*, could the Modules cache contain references to *each* import path condition so that the resolution could hop around the different conditions?

Okay, thanks. I was just wondering because if the `default` condition is cached, but the user is trying to get a different condition, this API (if it checks the cache)...

Adding stalled label, as @aduh95 left comments that were never addressed.

Hi! Do we think this feature would deprecate `util.styleText`?

Thanks for the information. I am +1 on this addition, and I look forward to its future!