WARNING in Circular dependency detected:

Hello Community.

The latest Jitsi updates i pulled this morning Compile with Warnings when downloading the Jitsi Project, running npm install, npm audit fix, and make dev.

It continues but it won’t let me see the first one that started it because the loop goes too far.
How can this be fixed?
See below:



Apparently you have circular dependencies which you need to fix. Recently we added a plugin to detect those:

Hi @damencho,
With this popping up in the Base Jitsi Project (not modified by me) how can we find the source?
I scrolled to the top of the terminal but this isn’t the first trigger.
You should be able to see this issue too if you pull the latest jitsi project from: https://github.com/jitsi/jitsi-meet

can’t you redirect the output to a file ?

I can try.
I tried “make dev > term.txt” but it only did a small output and didn’t show the warnings.
What Command should I run to output it?

I see. Maybe @saghul may have better idea.

maybe you did not wait enough ? Itried it and it outputed

WARNING in Circular dependency detected:
connection.js -> modules/UI/authentication/AuthHandler.js -> connection.js

the numerous following warnings are just warnings.
The true failure was

ERROR in ./node_modules/rnnoise-wasm/dist/index.js
Module not found: Error: Can’t resolve ‘fs’ in ‘/home/gp/dev/jitsi-meet/node_modules/rnnoise-wasm/dist’
@ ./node_modules/rnnoise-wasm/dist/index.js 8:1065-1078
@ ./react/features/stream-effects/rnnoise/index.js

Mine never got that far.
Waited an hour and only got this.

rm -fr libs
mkdir -p libs
./node_modules/.bin/node-sass css/main.scss css/all.bundle.css &&
./node_modules/.bin/cleancss css/all.bundle.css > css/all.css ;
rm css/all.bundle.css
Rendering Complete, saving .css file…
Wrote CSS to /Users/me/Documents/company/jitsi-meet/css/all.bundle.css
cp
node_modules/rnnoise-wasm/dist//rnnoise.wasm
libs
cp
node_modules/lib-jitsi-meet//lib-jitsi-meet.min.js
node_modules/lib-jitsi-meet//lib-jitsi-meet.min.map
node_modules/lib-jitsi-meet//connection_optimization/external_connect.js
node_modules/lib-jitsi-meet//modules/browser/capabilities.json
libs
cp
node_modules/libflacjs/dist/min//libflac4-1.3.2.min.js
node_modules/libflacjs/dist/min//libflac4-1.3.2.min.js.mem
libs
./node_modules/.bin/webpack-dev-server --detect-circular-deps
e[34mℹe[39m e[90m「wds」e[39m: Project is running at https://localhost:8080/
e[34mℹe[39m e[90m「wds」e[39m: webpack output is served from /libs/
e[34mℹe[39m e[90m「wds」e[39m: Content not from webpack is served from /Users/me/Documents/company/jitsi-meet
e[34mℹe[39m e[90m「wdm」e[39m: Compiled with warnings.

Yeah, redirecting stderr should do

make dev &>myterm.txt

you should have seen error messages on the console with a simple >.

That worked perfect. Here is the output.
term.txt (288.2 KB)

your project compiled successfully. The many warnings come from a code reorganization that is still ongoing (see git show 6e679f952f934264ec2b528a3646dc79c3159483) - this is a bane of so-called ‘modern’ projects. I guess that this circular dependency detection was added to help in the said ‘refactoring’. Problems that have existed before are now visible. That’s all there is to it I think. Sigh.

Facing similar warnings of circular dependency and the project does not launch with these warnings.
Has anyone solved this problem? Please share your findings.

hello @abhilashahyd,
as gpatel-fr mentioned, the project still compiles successfully so there’s nothing for us to change or do currently.

We are just seeing the current circular dependencies in the project which the Jitsi Team appears to be examining.
Thanks!

1 Like