Future of Nessie#165

> First off, I want to start by thanking everyone who has contributed to and supported Nessie 🎉 Prisma for Deno is almost fully supported natively with the recent NPM compatibility. This means that my original purpose with Nessie, namely database migration management, is fulfilled by a much more powerful tool. While Nessie still has a use-case, I no longer have the time nor need to maintain it for free 😬 The future of Nessie is then unfortunately very clear. While it started as a fun project to extend upon the, at the time, rather small module selection of Deno, and continued as a semi-popular db tool for projects, it is now time to hand in the towel. As soon as there is full support for Prisma in Deno, this repo is planned to be archived, or at the very least have issues, PRs, and actions deactivated (while keeping discussions). Since there might still be users of Deno who do not want to switch to Prisma due to the overhead or limitations, I will offer two options: 1. Someone forks this repo and continue the work (or you can fork it yourself) 🍴 2. This project receives the sponsoring of €500 per month to continue with maintenance support, and additional funding for specific features (estimated at around €100 per hour of work) 💵 > Feel free to comment your thoughts in this issue 😊 Links for Prisma+Deno: - https://www.prisma.io/docs/guides/deployment/deployment-guides/deploying-to-deno-deploy - https://deno.land/manual/node/how_to_with_npm/prisma - https://github.com/prisma/prisma/issues/2452 - https://deno.com/blog/persistent-data-npm#prisma