Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

133
Views
Accessing non-existent property 'padLevels' of module exports inside circular dependency

I just > npm i -g phonegap@9.0.0 and > phonegap --version.
It says not only 9.0.0 but also:

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

when I > node --trace-warnings ..., I got this:

internal/modules/cjs/loader.js:883
  throw err;
  ^

Error: Cannot find module 'C:\Users\twori\...'
[90m    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)[39m
[90m    at Function.Module._load (internal/modules/cjs/loader.js:725:27)[39m
[90m    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)[39m
[90m    at internal/main/run_main_module.js:17:47[39m {
  code: [32m'MODULE_NOT_FOUND'[39m,
  requireStack: []
}

I did only install and check version. Why does the phonegap module throw this error?
My teacher and other students go well with this, but only I can't do nothing.

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

After I updated my node from version 12 to version 14, I also faced the same warning. In my case, this warning was coming due to an older version of surge. after updating surge, the warning was gone. If you have surge installed in your system then update it to the latest version. You can run this command to update surge to the latest version:

  sudo npm i -g surge
over 4 years ago · Santiago Trujillo Report

0

That the node version was too high. Previously, the 14+ version used by the latest was used. After switching back to the 12 version, there would be no such problem.

Mac command

sudo n 12.0.0
over 4 years ago · Santiago Trujillo Report

0

Solved Root Cause

exports inside circular dependency

👆 This phrase gave hint to solve the same issue for me, it seems that newer NodeJS versions no longer allows circular dependencies.

Eg - There are two files - FileA.js, FileB.js

Where FileA.js has

const FileB = require("FileB");

and FileB.js has

const FileA = require("FileA");

After removing one of these circular dependencies by modifying either FileA.js or FileB.js, it was solved!

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!