Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

D3 latest version is using older version of d3-array #3505

Closed
cdeepshikha23 opened this issue Jun 10, 2021 · 7 comments
Closed

D3 latest version is using older version of d3-array #3505

cdeepshikha23 opened this issue Jun 10, 2021 · 7 comments

Comments

@cdeepshikha23
Copy link

cdeepshikha23 commented Jun 10, 2021

Have installed and using latest version (6.7.0) of d3 package.

This is still installing the older version of d3-array package which is 2.12.1 .

While using the latest version of d3 package below is the error that occurred.

Screenshot 2021-06-10 at 9 09 17 PM

@Fil
Copy link
Member

Fil commented Jun 10, 2021

The new d3-array will be bundled with d3@7 which is not out yet.

@Fil Fil closed this as completed Jun 10, 2021
@Narinderg
Copy link

But, then the current latest d3 package is giving error aa mentioned.

@Fil
Copy link
Member

Fil commented Jun 10, 2021

How can we reproduce the error?

@curran
Copy link
Contributor

curran commented Jun 10, 2021

It looks like the environment or build tool there does not support ES6 arrow functions.

@daftspaniel
Copy link

Get the same error running Jest in CI mode but not locally. Still looking into this issue but seems to be something to do with babel-jest not processing cumsum.js even if the modules are in the transform list.

@cederom
Copy link

cederom commented Aug 22, 2021

Yup. BLOCKER. D3 seems broken because of that D3-ARRAY Unexpected Token problem. I am using it wit React 16.13.1 and React Native 0.63.4 and Node 16.6.1. https://stackoverflow.com/questions/68376430/d3-giveing-error-of-unexpect-token-on-import

@cederom
Copy link

cederom commented Aug 23, 2021

Turns out to be Babel compiler bug, should be fixed with babel/babel#13581, thank you @mbostock :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants