There is a community fork of Crossfilter, which is probably what you are talking about :-) It is under the Crossfilter organization at
https://github.com/crossfilter I want to be clear that the Square people are still doing some bug-fix maintenance on their repository and the npm module under Crossfilter is the Square one. They do good work, but some of us wanted to see a little more movement. Therefore the fork.
I’ve done some work on getting Crossfilter running in a WebWorker. That work is here:
https://github.com/crossfilter/crossfilter-async The promise-based API there should be working well, but it is not compatible with dc.js. There is partly done work in that repository developing a wrapper that is compatible with dc.js.
It’s worth noting that if your data won’t load in Crossfilter in the main thread, then it won’t load in a WebWorker either. They both have the same memory constraints, to the best of my knowledge. If that’s the case, then you’ll want to look at a server-side solution like nanocubes or the mongoDB-based solution that was just posted to the list. If, on the other hand, you are just trying to improve main thread responsiveness, then the WebWorker approach is the way to go and I’d welcome help or testing on the crossfilter-async work if you’re willing to do that.
Thanks,
Ethan