fix: Add option to disable generator via env var

README.md

@@ -50,6 +50,11 @@ npx prisma generate
 | exclude   | Comma-separated list of model names to exclude from the top-level of the generated app (NOTE: If the 'include' option is used, this exclusion list will be ignored) |               | false    |
 | depth   | Maximum recursion depth for your models. (Changing this for large data models is not recommended, unless you filter down your models with the 'include' or 'exclude' flags also.) |     5          | false    |
 
+### Disabled
+To disable Nexquik from generating during a Prisma generate, add the following environmental variable.
+```zsh
+DISABLE_NEXQUIK=true
+```
 
 ## Examples
 ```prisma

src/cli.ts

@@ -15,6 +15,10 @@ const defaultPrismaSchemaPath = "schema.prisma";
 
 export async function run(options?: GeneratorOptions) {
   try {
+    const disabled = process.env.DISABLE_NEXQUIK === "true";
+    if (disabled) {
+      return console.log("Nexquik generation disabled due to env var");
+    }
     console.log(
       chalk.bgYellow.blue.bold(
         figlet.textSync("Nexquik", {

templateRoot/.env

@@ -4,4 +4,5 @@
 # Prisma supports the native connection string format for PostgreSQL, MySQL, SQLite, SQL Server, MongoDB and CockroachDB.
 # See the documentation for all the connection string options: https://pris.ly/d/connection-strings
 
-DATABASE_URL="file:./dev.db"
+DATABASE_URL="file:./dev.db"
+DISABLE_NEXQUIK=true

templateRoot/package.json

@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "private": true,
   "scripts": {
-    "dev": "prisma db push --accept-data-loss && next dev",
+    "dev": "npm run generate && next dev",
     "reset": "prisma migrate reset --force",
     "build": "next build",
     "start": "next start",
@@ -27,7 +27,7 @@
     "@types/react": "18.2.20",
     "@types/react-dom": "18.2.7",
     "autoprefixer": "^10.4.15",
-    "nexquik": "^2.0.3",
+    "nexquik": "*",
     "postcss": "^8.4.28",
     "tailwindcss": "^3.3.3"
   }