has-flag.js - seems to assume cli use, causing issue during synchronous module loading

[YeeP79]

The issue looks to be here:
https://github.com/DABH/colors.js/blob/master/lib/system/has-flag.js#L28

Node is just loading all imports into memory like it always does, and an error shows up:

Some debugging ahead of time will show that neither argv nor process.argv are defined.

Looking for any suggestions as to what can cause this. As the dependency chain comes from winston, I would image you would be seeing more issues raised if it was a straight up bug. Thank you

[valueof]

I was just dealing with a similar issue. In our case, we have a pretty generic Next app. We've decided to add winston for structured logging and this error pops up only when logging is being added to Next Middleware (middleware.ts). I believe this happens because middleware uses Edge Runtime which doesn't have process.argv.

For now, I've moved logging code out of middleware. If I initialize the logger anywhere in server-side pages/api it seems to work fine.

[axelvaindal]

I just had the same issue with Next 13 using app directory.

As stated by @valueof, running winston logger inside middleware breaks. I've also moved my logger out for now.

[copini]

Ran into the same issue using Next 13 (middleware + app directory). Was able to fix it locally using yarn patch, applying the same minor change as in PR #44.

[DABH]

This has been closed and released in v1.6.0. Thanks all!