I have a very strange error with wrappers 607. It ...

# react

[Björn Lilleike]

I have a very strange error with wrappers 607. It says "export 'default' (imported as 'ButtonBase') was not found in '../ButtonBase' (possible exports: getTouchRippleUtilityClass, touchRippleClasses)".
Resulting in Module not found errors.

All colleagues and the gitlab can build without this error.
I am running a clean checkout and cleared all caches. I even reinstalled intellij - I am running out of ideas what couldd be different on my system causing this problem.

[turansky]

cc @aerialist

[aerialist]

Hi @Björn Lilleike, try to remove yarn.lock and rebuild. Should helps

[Björn Lilleike]

Creates changes in yarn.lock, but the error remains

[Björn Lilleike]

The same branch works at three other PC. We still try to understand, if there is any hidden location for caches in the kotlin/js build other then in the project build/.gradle and the users .gradle

[aerialist]

Try to update wrappers. Will it help?

[Björn Lilleike]

Moving up to 608 removes the base-error and introduces a Module not found: Error: Can't resolve '@popperjs/core' in '\build\js\node_modules\@mui\base\Popper' - this kind of error we had befor and worked around it by explicitly importing the '@popperjs/core' - which does not work any more as a fix

[Björn Lilleike]

We don't want to move higher on the wrappers at the moment but wait for the current MUI-Upgrades to be completed, before we adapt out codebase.

[Björn Lilleike]

We would really like to understand, where this different build behaviour could have its source. For all we know, with yarn.lock in git it should be synchronized for each dependency.
The error with "Module @popperjs/core not found" is on some machines, but not on all.

[Björn Lilleike]

I get the same error, with the current kotlin-mui-showcase.:
"@popperjs/core not found in ..\kotlin-mui-showcase-80eaea8a542612c03e864b34f0378c4675d9f5c1\build\js\node_modules\@mui\base\Popper"

It is available in the buildpath under \js\nodemodules\@popperjs\core\dist\esm\...

[Björn Lilleike]

@aerialist This also happens on the latest main. I removed any known influence from my computer and am really lost what happens there.

[Björn Lilleike]

Update: Comparing the fresh, broken build with on at a colleague shows missing files in the popper. All grey files are missing and they haven't been created new on the working build either since early July.

[aerialist]

@Björn Lilleike, checked it myself on kotlin-mui-showcase - works fine.
I even upgrade yarn.lock - still fine.

I would also recommend you to try clean clean start of kotlin-mui-showcase app.
Please do next steps and share your result:
• clean gradle caches folder manually here - /Users/<username>/.gradle/caches
• ./gradlew clean
• ./gradlew --stop
• ./gradlew build
• ./gradlew jsRun -t

[Björn Lilleike]

Finally working! There was another cache in /Users/<username>/AppData/Local/Yarn/Cache/
This was broken and got copied into the project.
Thank you for checking and supporting and thank you very much for your efforts strengthening kotlin/js with react+mui

[aerialist]

You're welcome