@zerva/bin - npm Package Compare versions

Comparing version 0.7.21 to 0.7.26

package.json

 {
   "name": "@zerva/bin",
-  "version": "0.7.21",
+  "version": "0.7.26",
   "description": "🌱 Zerva Command Line Tool",
@@ -37,3 +37,3 @@ "bin": {
   },
-  "readme": "# 🌱 @zerva/bin\n\n**Sub-project of [Zerva](https://github.com/holtwick/zerva)**\n\nIn your `package.json` you might want to add these lines:\n\n```json\n\"scripts\": {\n  \"start\": \"zerva\",\n  \"build\": \"zerva build\",\n  \"serve\": \"node dist/main.cjs\"\n},\n```\n\nZerva uses [esbuild](https://esbuild.github.io) to create both the development server code and the production code. You can take advantage of conditional building using [defines](https://esbuild.github.io/api/#define). This can be used to have code that avoids certain imports or otherwise unneed stuff in production mode. I.e. in your code you can do stuff like this:\n\n```ts\nif (ZERVA_DEVELEPMENT) {\n  /* do something */\n}\n```\n\nValid defines are:\n\n- `ZERVA_DEVELOPMENT` is `true` when started as `zerva`\n- `ZERVA_PRODUCTION` is `true` when started as `zerva build`\n\nFor better compatibility the defines can also be accessed as `process.env.ZERVA_DEVELOPMENT` and `process.env.ZERVA_PRODUCTION`.\n"
+  "readme": "# 🌱 @zerva/bin\n\n**Sub-project of [Zerva](https://github.com/holtwick/zerva)**\n\nIn your `package.json` you might want to add these lines:\n\n```json\n\"scripts\": {\n  \"start\": \"zerva\",\n  \"build\": \"zerva build\",\n  \"serve\": \"node dist/main.cjs\"\n},\n```\n\nZerva uses [esbuild](https://esbuild.github.io) to create both the development server code and the production code. You can take advantage of conditional building using [defines](https://esbuild.github.io/api/#define). This can be used to have code that avoids certain imports or otherwise unneed stuff in production mode. I.e. in your code you can do stuff like this:\n\n```ts\nif (ZERVA_DEVELEPMENT) {\n  /* do something */\n}\n```\n\nValid defines are:\n\n- `ZERVA_DEVELOPMENT` is `true` when started as `zerva`\n- `ZERVA_PRODUCTION` is `true` when started as `zerva build`\n\nFor better compatibility the defines can also be accessed as `process.env.ZERVA_DEVELOPMENT` and `process.env.ZERVA_PRODUCTION`.\n\n```\nnpm install -D @zerva/bin @zerva/core @zerva/http \n```"
 }

README.md

@@ -29,1 +29,5 @@ # 🌱 @zerva/bin
 For better compatibility the defines can also be accessed as `process.env.ZERVA_DEVELOPMENT` and `process.env.ZERVA_PRODUCTION`.
+
+```
+npm install -D @zerva/bin @zerva/core @zerva/http 
+```

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

449583

increased by0.03%

Number of lines in readme file

32

increased by10.34%

No dependency changes