Error on fresh installation

[jairusd]

Describe the bug
after clean installation, i'm getting error with export default from inside the package

Expected behavior
should run without problem

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: windows 10
• Browser chrome
• Version 75.0.3770.142 (Official Build) (64-bit)

Additional context
Add any other context about the problem here.

[coodysk8er]

the same here. even with webpack 'js' babel loader including /node_modules/

[rajbits]

Facing the same issue here.. Tried couple of earlier versions too, seeing the same behavior.
Using create-react-app with hooks.

Upgrade to the latest node and create react app 2 and the error is gone.
@jairusd - what's your node environment?

[jairusd]

Facing the same issue here.. Tried couple of earlier versions too, seeing the same behavior.
Using create-react-app with hooks.

Upgrade to the latest node and create react app 2 and the error is gone.
@jairusd - what's your node environment?

I just upgraded to 12.6.0 and refreshed my deps to test it out, unfortunately, I'm still getting the same error.. Also tried LTS... I'm on a custom webpack configuration ssr environment. :(

[Topppy]

same problem +1. and when I try to use react-dnd-cjs, got another problem.

• os: mac
• electron 4.1.3
• electron-react-boilerplate

[Skylsmoi]

I'm having the same issue.
I just upgraded Babel to 7.4+ with the switch from @babel/polyfill to core-js so I'm yet not entirely sure where my error comes from.
I'll look closely at this thread though.

[jairusd]

I'm having the same issue.
I just upgraded Babel to 7.4+ with the switch from @babel/polyfill to core-js so I'm yet not entirely sure where my error comes from.
I'll look closely at this thread though.

same man.. i'm on core-js 3

[rajbits]

fwiw, with due respect to react-dnd, it did not work well with react-virtualized (which is a must have for me). I moved on to use react-sortable-hoc and the combo works best for me.

[tom-james-watson]

I had the same problem - they're directly exporting ES6 on react-dnd. Instead, just use the drop-in-replacement react-dnd-cjs and it should work fine.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.