fix: use cross-env for dev scripts

The default dev scripts were changed to invoke dotenv, but dotenv-cli is not installed in the project. This caused npm run dev to fail with 'dotenv: command not found'.

Use the existing cross-env binary directly for the default and basic auth dev scripts.

Author: adityathebe

package-lock.json

@@ -163,9 +163,9 @@
     ]
   },
   "scripts": {
-    "dev": "dotenv run cross-env next dev",
+    "dev": "cross-env next dev",
     "dev:canary": "cross-env NEXT_PUBLIC_APP_DEPLOYMENT=CANARY_CHECKER next dev",
-    "dev:basic": "cp middleware.basic.ts middleware.ts && dotenv run cross-env next dev",
+    "dev:basic": "cp middleware.basic.ts middleware.ts && cross-env next dev",
     "dev:clerk": "cp middleware.clerk.ts middleware.ts && cross-env next dev",
     "start": "cross-env next start",
     "build": "cross-env NODE_OPTIONS=--max-old-space-size=8192 node -v && cross-env NODE_OPTIONS=--max-old-space-size=8192 NODE_ENV=production next build",