Typescript typings have no default export

[firsttris]

Holla,
before it was possible to import react-day-picker in typescript using the following construct:

import DayPicker from 'react-day-picker';

In version 6.2.1 the tsc compiler complains that 'react-day-picker' has no default export.

but if a change:

// **\node_modules\react-day-picker\types\index.d.ts
// TypeScript Version: 2.2

import { DayPicker } from "./DayPicker";
// We need to use 'export =' to be compatible with the 'module.exports = DayPicker.default || DayPicker' syntax
// in DayPicker.js in the final NPM package.
export = DayPicker;

to

// **\node_modules\react-day-picker\types\index.d.ts
// TypeScript Version: 2.2

import { DayPicker } from "./DayPicker";
// We need to use 'export =' to be compatible with the 'module.exports = DayPicker.default || DayPicker' syntax
// in DayPicker.js in the final NPM package.
export default DayPicker;

the import is working again.
Im using 6.2.1 with the integrated typings.

whats the correct way to import in typescript ?

regards
Tristan

[PeterKottas]

This is definitely broken/undocumented. I see the same problem.

[firsttris]

Currently its possible to use import DayPicker = require('react-day-picker'); to get working typings with 6.2.1

[gpbl]

#539 has a longer discussion which I'd like to link here.

[gpbl]

I'd just plan a major release with the right export. I'd like also to remove the common.js default exports which are the root of all the problems 😄

[gpbl]

c221e2d should fix the issues