VelSharon
commented
1 year ago I was able to resolve the first error (@fullcalendar/react) but I'm stuck with a vdom error.
Module not found: Error: Can't resolve './vdom' in 'C:\Users\Prasanna\OneDrive\Desktop\course-schedulizer\client-course-schedulizer\node_modules\@fullcalendar\common' Did you mean 'vdom.js'? BREAKING CHANGE: The request './vdom' failed to resolve only because it was resolved as fully specified (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"'). The extension in the request is mandatory for it to be fully specified. Add the extension to the request.
When I inspected the files in the folders mentioned in the error message, there are multiple instances of '/vdom' and while I did try to manually replace them with './vdom.js', I still have the same error message but in a completely category of node_modules now. I'm sure there is a better way of updating these instances than manually having to replace them. I tried running npm install vdom but not sure if it helped.
These calendar and fullcalendar errors seem to pop up whenever there is an update to the code. Not sure how specific this issue is to our devices, but we have run into these errors multiple times while running the app on the development server. Sometimes running npm install would fix it but that does not seem to be a long-term solution. Currently, I am facing these errors on my device after I tried to update the dependencies. Based on my research, I do believe it is an issue with the fullcalendar dependency but updating it has not solved the issue.
I am running the application (npm start) on the production branch through git bash. And there are about 171 errors, most of which are about calendar/fullcalendar. The results are almost identical to running it on the ubuntu terminal as well.