Merge pull request #11 from expatfile/development

chore: 🔖 release stable version

Author: HofmannZ

README.md

@@ -21,18 +21,19 @@ development, and Next.js is no exception.
 
 Next.js supports [environment variables][nextjs-env-vars], but only at
 build time. This means you must rebuild your app for each target environment,
-which violates the principle. And it is the most common approach nowadays. But
-what if you want, or need, to follow the build once, deploy many principle?
+which violates the principle. But what if you want, or need, to follow the build
+once, deploy many principle?
 
 ### The solution 🤓
 
 `next-runtime-env` solves this problem by generating a JavaScript file that is
 loaded by the browser and contains the environment variables. We generate this
 file at runtime, so you don't have to declare your environment variables at
-build time. This approach is also compatible with
-[static site generation][static-generation-link], and it works on the server as
-well. It also supports middleware, so you can use it to populate your
-environment variables in your API routes.
+build time.
+
+Our approach is compatible with
+[static site generation][static-generation-link], and it also supports
+middleware.
 
 ### Getting started 🚀
 

package.json

@@ -31,12 +31,15 @@
     "url": "https://github.com/expatfile/next-runtime-env/issues"
   },
   "homepage": "https://github.com/expatfile/next-runtime-env#readme",
+  "dependencies": {
+    "chalk": "^4.1.2"
+  },
   "devDependencies": {
     "@types/eslint": "^8.37.0",
     "@types/jest": "^29.5.1",
     "@types/node": "^18.16.3",
-    "@typescript-eslint/eslint-plugin": "^5.59.1",
-    "@typescript-eslint/parser": "^5.59.1",
+    "@typescript-eslint/eslint-plugin": "^5.59.2",
+    "@typescript-eslint/parser": "^5.59.2",
     "audit-ci": "^6.6.1",
     "eslint-config-airbnb-base": "^15.0.0",
     "eslint-config-prettier": "^8.8.0",