.17 -> .18 initialization

Do you want to request a feature or report a bug?

bug

What’s the current behavior?

.17 initializes correctly with:

import * as moment from 'moment';
import BigCalendar from 'react-big-calendar';

and then

BigCalendar.momentLocalizer(moment);

But when I use .18, the BigCalendar variable isn’t initialized, so the momentLocalizer method doesn’t exist and it throws an error that BigCalendar is undefined. Did something change from .17 to .18 that changed the initialization?

What’s the expected behavior?

BigCalendar object should be initialized and ready to render.

Sorry for the relative paucity of details. Given that this issue is with the barest beginning of use, I feel like it’s pretty quick to reproduce.

[josdejong]

Same issue here using a react+typescript application (create-react-app with react-scripts-ts).

In our case BigCalendar was initialized correctly when in develop mode, but when creating a bundle the variable was undefined.

As a workaround I use require instead of import:

const BigCalendar = require('react-big-calendar')

[ggsjyoon]

It’s okay. I’m not using no-var-requires.