TypeScript definitions are out of date

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

• I found a bug
• I want to propose a feature

What is the current behavior? Latest version of react-dropzone at the time of submitting this issue is 4.1.3, however the latest available version of @types/react-dropzone is 3.13.1 and it’s already missing at least one property definition.

If the current behavior is a bug, please provide the steps to reproduce.

1. Add a Dropzone component to your page

   import * as Dropzone from 'react-dropzone';
   

2. Try to define the disabledClassName

   <Dropzone
       disabledClassName="my-disabled-classname"
   >
   

3. Receive a transpilation error:

   error TS2339: Property 'disabledClassName' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Dropzone> & Readonly<{ children?: ReactNode; }> & ...'.
   

Same seems to be happening to acceptClassName.

What is the expected behavior? Being able to use all properties available in the current version.

[benbayard]

A note: in TS you should not import React-dropzone with * as imports. This module is exported as common JS in its source. You should use import Dropzone = require('react-dropzone);

[FlayaN]

@ashok-sc It seems like the typescript-definition is still wrong.

I got it to work using:

"@types/react-dropzone": "4.1.0",
"react-dropzone": "4.1.3

Either you can change typing locally row 51 in index.d.ts export = Dropzone; => export default Dropzone; But that will get overwritten of course…

So I instead added this when I import the module:

import * as Dropzone2 from "react-dropzone";
const Dropzone: any = Dropzone2; // @types/react-dropzone 4.1.0 exports wrong

And this works both in typescript and runtime…