jquense / react-big-calendar

gcal/outlook like calendar component
http://jquense.github.io/react-big-calendar/examples/index.html
MIT License
7.57k stars 2.2k forks source link

ERROR in ./node_modules/react-big-calendar/dist/react-big-calendar.esm.js 6:0-62 #2533

Closed peterzanetti closed 3 months ago

peterzanetti commented 4 months ago

Check that this is really a bug

Reproduction link

n/a

Bug description

On a fresh install of react-big-calendar and rendering with the most basic example, I am immediately getting this error and it won't render. Please assist.

Module not found: Error: Package path ./helpers/esm/callSuper is not exported from package ../node_modules/@babel/runtime

Expected Behavior

Renders the calendar

Actual Behavior

Fails

react-big-calendar version

1.11.2

React version

18.2.0

Platform/Target and Browser Versions

macOS

Validations

Would you like to open a PR for this bug?

arepp23 commented 4 months ago

Having the same issue on a next.js 14.0.3 typescript app with node 18.17.0

TarasPotsikaylo commented 3 months ago

Having the same issue on a react 18.2.0 typescript app with node 18.13.0

dcrec1 commented 3 months ago

Same here.

Jobin-S commented 3 months ago

same here react ^17.0.2

Jobin-S commented 3 months ago

npm i @babel/runtime

Running this has fixed this issue. But the style (CSS) is not loading

image
Jobin-S commented 3 months ago

@peterzanetti do you find any alternative? I have to submit the calendar event today. feked up :(

qujunxian commented 3 months ago

@Jobin-S You can lower the version to 1.8.7 to temporarily solve this problem :)

marcocinus91 commented 3 months ago

I had the same problem. Update to the latest version of @babel/runtime, then update Big Calendar. Check if another @babel directory exists inside your react-big-calendar directory and delete it.

sethmcleod commented 3 months ago

Looks like this was introduced in v1.10.1 with the updates to yarn.lock

Ladvace commented 3 months ago

same problem here, did you find any solution?

cutterbl commented 3 months ago

Please see @marcocinus91 comment above for the solution to this issue.

joeplaa commented 1 month ago

I solved it by adding "@babel/runtime": "^7.24.6" to the resolutions. When running yarn install, it removed duplicate (stale) entries. After that I removed the "resolution" and it still works.

"resolutions": {
  "@babel/runtime": "^7.24.6"
},