Refine•3y ago

Compile Error After Update Refine and Antd

I just update refine and other things but i got error. Could you help me please?

package.json1.88KB

brilliant-lime•12/25/22, 3:26 PM

Compiled Error when update refine antd can you follow this post please ? it's seems similar error

brilliant-lime•12/25/22, 3:27 PM

can you try npm install after removing node_modules

living-lavenderOP•12/25/22, 3:33 PM

I already try that but nothing changed. I delete node_modules, then run npm clear cache --force, then npm verify cache and then npm install but still got error

efficient-indigo•12/25/22, 3:34 PM

Can you try with removing the lock file?

living-lavenderOP•12/25/22, 3:35 PM

I also get this error too

living-lavenderOP•12/25/22, 3:35 PM

I will try it.

efficient-indigo•12/25/22, 3:37 PM

Thank you, we’re investigating the issue

brilliant-lime•12/25/22, 3:44 PM

maybe craco can cause problems.

can you uninstall craco and try again ?
antd removed less support. probably you dont need craco anymore.

brilliant-lime•12/25/22, 3:46 PM

if it works we will look into the craco fix with core team tomorrow.
but probably you don't need craco anymore because antd dropped less support

living-lavenderOP•12/25/22, 4:41 PM

Hi, i just delete lock file and node modules then insall and now it's ok. But about this error, i don't what it cause but it seems nothing for me for now. Thank you for your support guys.

living-lavenderOP•12/25/22, 4:42 PM

about craco, can i still write css with less? Does it need any configuration?

brilliant-lime•12/25/22, 5:54 PM

according to antd, u can with this : https://ant.design/docs/react/migration-v5#less-migration

living-lavenderOP•12/25/22, 6:42 PM

thank you for your all support, I'll look into it

living-lavenderOP•12/25/22, 7:22 PM

I want to ask one more question, when i stop app with ctrl+c combination, i think it still running on backgroud. I keep getting this error.

efficient-indigo•12/25/22, 7:23 PM

Can you share your response of npm run refine — whoaminpm run refine — whoami

living-lavenderOP•12/25/22, 7:24 PM

Yes, there it is

efficient-indigo•12/25/22, 8:52 PM

Thank you for sharing that. I guess there’s an issue with our runner or in any helper or the commands we ran that they dont handle their child processes properly for SIGINT signal to kill the app or a problem with our helpers that does not propagate that signal well. I will investigate this issue and resolve it as soon as possible

Sorry for the trouble.

Btw, does this happen all the time or just happens randomly, and also does it happen after you kill the app and wait for couple seconds and restart?

living-lavenderOP•12/25/22, 8:59 PM

I feel like it happens randomly, because now i will change port until 3003, after that i try again port 3000, it's work. It seems it can't kill directly, developer must wait couple seconds, i'm not sure exactly how much.