		{
		"name": "@zerva/bin",
		"version": "0.7.17-beta.2",
		"version": "0.7.17-beta.3",
		"description": "🌱 Zerva Command Line Tool",
		@@ -36,3 +36,4 @@ "bin": {
		"global": "pnpm -g ln"
		}
		},
		"readme": "# 🌱 @zerva/bin\n\nSub-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"
		}

@zerva/bin - npm Package Compare versions

New alerts