-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Circular Dependencies in @rjsf\core when using Rollup #2341
Comments
I just switched to esbuild (which is sick) and the error isn't showing up anymore... 🤷♂️ |
I have the same (or a very similar) problem! Even though it still compiles somehow, it is quite annoying to see this error in the logs all the time. Would be great if something could be done about that! |
This needs to be fixed |
Can you help fix it? 🙂 |
Oh, I don't actually understand the cause of the problem... Just wanted to point out that it's still present and reproducible. |
It seems the Perhaps we just need to move the function to a different file? |
Fixed in the v5 beta, see the 5.x migration guide |
Prerequisites
Description
Rollup is reporting
@rjsf\core
having multiple circular dependencies:The system still seems to be working as far as I can tell so far, but I've seen such errors break things in the past so I find it concerning. I expect most people are using webpack to compile their code, so I suspect this error is only showing up when using Rollup.
I snooped around at the code and these circular dependencies do seem to be real, though I'm not sure what kind of impact it's actually having.
Steps to Reproduce
I'm using the Material UI plugin like so:
I'm not sure what else may be relevant here...
I'm using
gulp-better-rollup
,@rollup/plugin-typescript
,@rollup/plugin-commonjs
,@rollup/plugin-node-resolve
,@rollup/plugin-json
when compiling with rollup.Expected behavior
Rollup should compile the code without finding any circular dependencies within
@rjsf
's code.Actual behavior
Rollup is complaining about the circular dependencies whenever recompiling the React code.
Version
You can usually get this information in your
package.json
or in the file URL if you're using the unpkg one.The text was updated successfully, but these errors were encountered: