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

export 'bin' (imported as 'd3Array') was not found in 'd3-array' #1822

Closed
4 tasks done
6axter82 opened this issue Apr 14, 2021 · 4 comments
Closed
4 tasks done

export 'bin' (imported as 'd3Array') was not found in 'd3-array' #1822

6axter82 opened this issue Apr 14, 2021 · 4 comments

Comments

@6axter82
Copy link

Bugs and Questions

Checklist

  • This is not a victory-native specific issue. (Issues that only appear in victory-native should be opened here)

  • I have read through the FAQ and Guides before asking a question

  • I am using the latest version of Victory

  • I've searched open issues to make sure I'm not opening a duplicate issue

The Problem

After updating to the latest version of victory 35.5.1
getting the following printout in terminal after 'yarn start':

WARNING in ./node_modules/victory-histogram/es/helper-methods.js 63:12-23
"export 'bin' (imported as 'd3Array') was not found in 'd3-array'
@ ./node_modules/victory-histogram/es/victory-histogram.js
@ ./node_modules/victory-histogram/es/index.js
@ ./node_modules/victory/es/index.js

@boygirl
Copy link
Contributor

boygirl commented Apr 14, 2021

@6axter82 thanks for opening this issue. Unfortunately, I'm not able to reproduce it. We did make some changes to how we build Victory's dist in the latest version, but the warning you're seeing looks like it's referencing the es source, so I wouldn't expect the resent set of changes to cause it. You can see the diff here: https://github.com/FormidableLabs/victory/pull/1819/files

@boygirl boygirl closed this as completed May 17, 2021
@JWess
Copy link

JWess commented Jul 20, 2021

I am seeing this exact same error, and I can't figure out why. My co-workers are not seeing the same issue. I have tried changing versions of Node/Npm, re-cloning my repo, installing with npm ci, blowing away my package-lock.json, etc. I am on Windows, and I use NVM in case that somehow helps, and we are using Craco to build our React app that was originally created with Create React App.

image

@mcserep
Copy link

mcserep commented Aug 31, 2021

I have the very same issue, only on Windows. Did anyone managed to solve it?
npm v6.14.11
node v14.16.0

@mcserep
Copy link

mcserep commented Sep 12, 2021

After some debugging it turned out if I execute npm start or npm run build in PowerShell, there is no issue, only when using the good old Command Prompt of Windows. Since there are separate .cmd and .ps1 scripts in the .bin folder of node_modules, there could be an issue with the Batch scripts.

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

No branches or pull requests

4 participants