[node v14.x+] Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency

[SwapnilSoni1999]

The new node version doesn't let process to start. whenever

$ forever start app.js

is executed it shows the following warning

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: bot.js
(node:14545) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:14545) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency

and after this if I check with forever list it shows no process is running.

(node:14574) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:14574) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
info:    No forever processes running

[kibertoad]

@SwapnilSoni1999 I'll take a look, thanks for the report.

[roblav96]

@kibertoad

On the following platforms:

Ubuntu 20.04 LTS

Package: nodejs
Version: 14.1.0-deb-1nodesource1

✅ 'padLevels' warnings
❌ script runs

Mac OS X 10.13.6

Package: node
Version: stable 14.1.0 (bottled)

✅ 'padLevels' warnings
✅ script runs

[CanadaHonk]

Me too, script doesn't run and I get the warnings - Node v14.2.0 (Arch Linux)

[SwapnilSoni1999]

Me too, script doesn't run and I get the warnings - Node v14.2.0 (Arch Linux)

same here checked on ubuntu 20.04 and archlinux too

[roblav96]

Please refer to #1075 for more info.

[SwapnilSoni1999]

Please refer to #1075 for more info.

please explain a bit how this issue is related to the issue you mentioned.
Thanks

[naeem518]

Same problem with Nodejs Ver 10 and forever 2.0 wont start on windows 10 server 2016... changed roblav96 suggestion #1075 in monitor to string for the file system for the pid and last line erase extra New Line... with same error but different node addresses every time complaining about padLevels... the process does not start ... please help

[kibertoad]

Unfortunately this cannot be easily fixed on forever side - reason for the problem is this - winstonjs/winston#1797

Best solution would be to drop dependency on Winston altogether and replace it with something like pino, but unfortunately that would take way more time than I currently have.

PRs welcome. In the meantime, I would recommend to use alternatives to forever, such as pm2 or nodemon on Node 14.

[kibertoad]

@SwapnilSoni1999 I don't think it should prevent application from starting, it's just a warning. As @naeem518 has mentioned, there was another problem, that was fixed in #1075, that might have prevented forever from working in certain cases. You can try forever 3.0.0 and see if it works any better for you.

[SwapnilSoni1999]

@kibertoad sure sir just give some time and I'll check

[sapics]

@kibertoad Thank you for releasing new version!
I confirmed that new version works without errors on linux with latest nodejs version.

[akircher]

Confirming with @sapics said.

I am on Ubuntu@16.04, Node@14.2.0. After upgrading from Forever 2.X to Forever 3.0.0, forever start still shows me the error

(node:9923) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:9923) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency

But at least the forever process starts and continues to run unlike before!

[sapics]

Hi @akircher !
It is not error, but warning. Thus, your program would work as you noticed.
The warning come from the other program (winston) which used by forever.

[robertmylne]

Still having this problem over a month from this being logged.

[SwapnilSoni1999]

Still having this problem over a month from this being logged.

which os?