Open jrgleason opened 9 years ago
Hey @jrgleason, sincere apologies for missing this issue! Just saw it now.
My first guess would be that in the Node version switch, the dependencies also changed, and with Node 12.7, you were using node-neo4j v1 instead of v2.
Is this still happening for you? Or did it resolve itself?
I have the following code...
This works fine under 12.4 but fails in 12.7 (using Windows 10). Can someone confirm? Any idea what may cause this?