Repository navigation
CLI prints a bunch of node warnings on Node.js 14.0.0 #5203
Description
Steps to reproduce
$ nvm install 14.0.0.
Downloading and installing node v14.0.0
(...)
Now using node v14.0.0 (npm v6.14.4)
$ npm i -g @loopback/cli
(...)
+ @loopback/cli@2.4.3
added 761 packages from 392 contributors in 78.492s
$ lb4 example todoCurrent Behavior
A lot of warnings are printed
(node:26892) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:26892) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'dirs' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'pushd' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'popd' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'echo' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'tempdir' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'pwd' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'exec' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'ls' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'find' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'grep' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'head' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'ln' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'mkdir' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'rm' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'mv' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'sed' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'set' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'sort' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'tail' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'test' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'to' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'toEnd' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'touch' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'uniq' of module exports inside circular dependency
(node:26892) Warning: Accessing non-existent property 'which' of module exports inside circular dependency
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
Expected Behavior
No warnings are printed.
While this bug is specifically describing Node warnings about "Accessing non-existent property", it would be eventually nice to get rid of request dependency too.
Link to reproduction sandbox
n/a
Additional information
$ node -e 'console.log(process.platform, process.arch, process.versions.node)'
darwin x64 14.0.0
Related Issues
See Reporting Issues for more tips on writing good issues
Activity
raymondfeng commentedon Apr 23, 2020
See nodejs/node#29935
It might be related to
shelljs.raymondfeng commentedon Apr 23, 2020
Running
NODE_OPTIONS="--trace-warnings" lb4confirms thatshelljsis the root cause.raymondfeng commentedon Apr 23, 2020
Duplicate of shelljs/shelljs#991
deepakrkris commentedon Apr 23, 2020
there is no immediate action available for this, will have to wait for a new release of shelljs
frbuceta commentedon Apr 27, 2020
If you allow me, I will close this issue. With the maintenance of the package-lock's it has been fixed