Eric N. Vander Weele
Eric N. Vander Weele
@mikehaas763, I'm still (slowly) working on it. It hasn't been a super high priority for me at the moment. However, there is probably a bit more refactoring work that is...
I did reach out to @mikehaas763 via the email on his GitHub profile page, but never received a reply :). I partially agree with @mikehaas763's assessment. However, some npm packages...
That part is the straight-forward part, the difficult part is properly piping that down to where it needs to get plugged in.
We shouldn't be modifying the vendor dependencies. Instead, we should modify `blpapijs.cpp` to handle the thrown exception. Can you provide an example that reproduces the issue?
@apaprocki, can you verify and (hopefully) close this? Thanks.
Commandeering this issue to track progress for only supporting node >= 0.12.x and io.js.
Branch [node-v0.12](https://github.com/bloomberg/blpapi-node/tree/node-v0.12) created to publicize progress.
8887947 now puts the hard requirement on what is supported. Going to create a milestone with some itemized issues that have been identified.
Created milestone [node >= 0.12.x and io.js >= 1.0.x](http://github.com/bloomberg/blpapi-node/milestones/node%20%3E=%200.12.x%20and%20io.js%20%3E=%201.0.x) with issues assigned.
@norphe, it appears this is during initialization; is that correct? Most likely these DLL load errors are due to improper library search paths with the host machine, not `blpapi-node` itself.