I always got the message as followed in my browser, no matter how I’ve changed the frontend.
I’m not sure if it is the problem of frontend.
Can anyone tell me what I can do to make it work?
And this is what I get when I try to “npm install” the frontend so that I think it’s the problem of frontend:
npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.14.5
npm WARN Found: @babel/core@7.12.3
npm WARN node_modules/@babel/core
npm WARN dev @babel/core@“7.12.3” from the root project
npm WARN 160 more (@babel/helper-compilation-targets, …)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer @babel/core@"^7.13.0" from @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.14.5
npm WARN node_modules/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining
npm WARN @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@"^7.14.5" from @babel/preset-env@7.14.5
npm WARN node_modules/@babel/preset-env
npm WARN
npm WARN Conflicting peer dependency: @babel/core@7.22.5
npm WARN node_modules/@babel/core
npm WARN peer @babel/core@"^7.13.0" from @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.14.5
npm WARN node_modules/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining
npm WARN @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@"^7.14.5" from @babel/preset-env@7.14.5
npm WARN node_modules/@babel/preset-env
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: react-native@0.70.6
npm WARN Found: react@17.0.0
npm WARN node_modules/react
npm WARN react@“17.0.0” from the root project
npm WARN 27 more (@gatsbyjs/reach-router, …)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@“18.1.0” from react-native@0.70.6
npm WARN node_modules/react-qr-code/node_modules/react-native
npm WARN peer react-native@"*****" from @react-native-community/art@1.2.0
npm WARN node_modules/react-qr-code/node_modules/@react-native-community/art
npm WARN
npm WARN Conflicting peer dependency: react@18.1.0
npm WARN node_modules/react
npm WARN peer react@“18.1.0” from react-native@0.70.6
npm WARN node_modules/react-qr-code/node_modules/react-native
npm WARN peer react-native@"*****" from @react-native-community/art@1.2.0
npm WARN node_modules/react-qr-code/node_modules/@react-native-community/art
up to date, audited 2741 packages in 24s
229 packages are looking for funding
run npm fund for details
137 vulnerabilities (1 low, 100 moderate, 35 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues possible (including breaking changes), run:
npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run npm audit for details.
My macos version is Ventura 13.4.1
As a start it might be best to describe your setup and provide background for the reader. Various forum readers have specialized skills in different areas and OSes that might be directly applicable to your needs.
For example, is your Seafile server CE or Pro (which version?), standalone install or Docker, a new installation or upgrade; are clients mixed or exclusively macOS, and so on.
If you can fill in some blanks it might help direct a solution.
-Thank you
My Seafile server is standalone installed by compling from the newest master branch of the repo.
For my question, it’s just about seahub which is written in Python and react.
I don’t think there are issues about seafile-clients for the time being, because I just have tried to run seafile-server, seahub backend and frontend meanwhile on my macOS Ventura 13.4.1, without any other clients running.