Accessing non-existent property: npm run build

[MeRahulAhire]

I haven't seen this in a while of my react development and want to know how can I work around it?

I'm trying to do a npm run build and Its giving me the following logs

> [email protected] build
> react-scripts build

Creating an optimized production build...
(node:8780) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:8780) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'dirs' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'pushd' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'popd' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'echo' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'tempdir' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'pwd' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'exec' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'ls' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'find' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'grep' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'head' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'ln' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'mkdir' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'rm' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'mv' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'sed' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'set' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'sort' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'tail' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'test' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'to' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'toEnd' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'touch' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'uniq' of module exports inside circular dependency
(node:8780) Warning: Accessing non-existent property 'which' of module exports inside circular dependency
Failed to compile.

Unknown browser query `dead`

and it doesn't even npm start node v17 so I down graded to v16+ lts. Any solution on what should I do?

[fatalchemist]

i ran into exactly the same circular dependency error, the following resolved the error though: upgrading my node version to the latest release with nvm install latest and updating my dependencies with yarn upgrade-interactive --latest cheers.

[MeRahulAhire]

I tried latest version of node v17 on windows but it doesn't even npm start

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[kkeri]

I got the same warnings in a project freshly created with create-react-app. It turned out that for some reason I had a fairly old version of react-scripts (0.9.5). I upgraded to 5.0.1 and the warnings disappeared.