Issue with crossfilter dependency
See original GitHub issueHi there, I have a small problem with running dc example (stock.js). I added the next dependencies to my package.json:
"dependencies": {
"colorbrewer": "^1.0.0",
"dc": "^2.1.1",
After that I got the next error: Uncaught Error: Cannot find module ‘crossfilter’. To fix this issue I changed node_modules/dc/index.js:
d3 = require("d3");
crossfilter = require("crossfilter2");
module.exports = require("./dc");
from crossfilter to crossfilter2. Could you please help me with this issue? What is the proper fix? Or it is a problem with crossfilter ? Thank you for your help in advance.
Issue Analytics
- State:
- Created 7 years ago
- Comments:20 (8 by maintainers)
Top Results From Across the Web
Solved: Circular dependency blocks cross filter
I have made a unique join key to establish a relationship between agents and pickups, data is coming in no problem and filtered...
Read more >crossfilter - npm
Start using crossfilter in your project by running `npm i crossfilter`. There are 38 other projects in the npm registry using crossfilter.
Read more >Filtering issues with dependencies | Atlassian Support
When planning work across multiple streams, filtering issues with dependencies helps to quickly narrow down any potential blockers that need ...
Read more >Avoiding circular dependency errors in DAX - SQLBI
This article explains the most common causes of the error, “A circular dependency was detected” in Power BI and Analysis Services.
Read more >Power BI > USERELATIONSHIP Vs. CROSSFILTER
Inkey. INKEY is your solution partner. Our focus is to deliver you in-time intelligent innovative solutions ("key") for the problems in ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As explained in #1214, this does not work in AMD environments, where this specifies the name of the file instead of the name of the module.
Sorry for the inconvenience - it seems that the only way to make both AMD and Webpack happy is to make http://github.com/crossfilter/crossfilter use the same name for its filename as for its NPM project name.
@gordonwoodhull yes, just tried it now. I can confirm that
resolve.alias
in webpack solves the issue with yarn and webpack. Thanks!