Bogdan Chadkin

I'm gonna propose flat bundles instead of transpiled files to have better control over size which users consume. We could start working on the next major release. What do you...

The case is controllable treeshaking. So we could provide the only one and safe way to use the library with only named exports. I think this is better since user...

I'd suggest to use https://github.com/que-etc/resize-observer-polyfill

Internals are quite messy yet. Gonna fix in following PRs.

Example ```js import GridLayout, { createDragApiRef } from 'react-grid-layout'; class App extends React.Component { dragApi = createDragApiRef(); onDrag = event => { if (this.dragApi.value) { const { x, y }...

Maintaining the same props (passed to grid) separatly is hard. Changes in lib may break UX implicitly for developer. Also right now it's not posible to maintain placeholder.

Modeling events with swapping states is also shot in the foot.

Importing function as a namespace is the biggest failure of typescript. Key-value object just cannot be a function. ```js import * as createReactContext from 'create-react-context'; ``` Some guys said me...

Workaround in every package is broken ecosystem.

Can't you play with some options to solve the problem on your side?