Md. Abu Taher
Md. Abu Taher
Using old nightmare is just a temporary solution.
Care to share your workaround code?
@bwbuchanan, I tried putting that preload.js, however, it was not fixed in.
I tested your solution, @bwbuchanan. And the result is as you can see.  Codes: ``` var Nightmare = require('nightmare'), path = require('path'), nightmare = Nightmare({ show: true, webPreferences: {...
Really +1 for this. I have multiple big app with multiple schema and wanted to migrate it to new cool nexus and prisma2, and we are impressed with prisma 2...
Sorry to bump the issue but I was thinking what is the current situation and what are forced to accept as the solution when migrating from prisma 1 to prisma...
We are going to move away from meteor version, and will create another version with vanila js (maybe next.js), prisma/hasura as database entry. I will ping you about the roadmap...
We will create and invite over the slack and few other community platforms, please wait. :D
This is a great opportunity to do some open source collaboration for [Hacktoberfest](https://hacktoberfest.digitalocean.com/).
@raynoppe please ping [email protected]