Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Npm registry version differs from github release

See original GitHub issue

Overview of the problem

I’m using react-rnd version [10.1.9] (see npm)

My browser is: Chrome (electron)

Steps to Reproduce

yarn add react-rnd
Version in package.json will be 10.1.9

Expected behavior

Version to be consistent with github releases (10.1.8 or 9.1.1)

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:11 (5 by maintainers)

Top GitHub Comments

3reactions

STRMLcommented, May 12, 2020

Thank you very much @NeroVanbiervliet. Because of your reproduction I was able to verify that react-draggable@4.4.0 fixes the original issue, and discovered another bundling issue that is fixed in 4.4.1.

@bokuweb thanks for your patience with me, I had a hare-brained idea to modernize the builds I was shipping to support umd, cjs, and modules - an exercise in futility to handle well, with the costs far outweighing the benefits. Most of that work is deleted in 4.4.1, and the only exposed build is ES5-compliant, unminified, CJS source.

2reactions

STRMLcommented, May 11, 2020

Hi - if any of you can recreate this error in React-Draggable 4.3.1 we’d be very happy to find out how you did it. There is no appreciable difference we can find in the bundling between 4.2.0 and 4.3.1, but many users are reporting this with no reproduction.

If someone could post a reproduction, we can get it fixed quickly.