pepr 0.2.8 → 0.2.9

package/README.md

@@ -48,6 +48,7 @@ pepr init
 npm run k3d-setup
 
 # Start playing with Pepr now
+# If using another local K8s distro instead of k3d, run `pepr dev --host host.docker.internal`
 pepr dev
 kubectl apply -f capabilities/hello-pepr.samples.yaml
 

package/dist/package.json

@@ -9,7 +9,7 @@
     "engines": {
         "node": ">=18.0.0"
     },
-    "version": "0.2.8",
+    "version": "0.2.9",
     "main": "dist/index.js",
     "types": "dist/index.d.ts",
     "pepr": {
@@ -67,7 +67,7 @@
         "@typescript-eslint/parser": "5.59.0",
         "ava": "5.2.0",
         "eslint": "8.39.0",
-        "nock": "13.3.0"
+        "nock": "13.3.1"
     },
     "ava": {
         "extensions": [

package/dist/src/cli/dev.js

@@ -17,7 +17,7 @@ function default_1(program) {
     program
         .command("dev")
         .description("Setup a local webhook development environment")
-        .option("-h, --host [host]", "Host to listen on", "host.docker.internal")
+        .option("-h, --host [host]", "Host to listen on", "host.k3d.internal")
         .option("--confirm", "Skip confirmation prompt")
         .action(async (opts) => {
         // Prompt the user to confirm if they didn't pass the --confirm flag

package/docs/cli.md

@@ -10,6 +10,7 @@ Initialize a new Pepr Module.
 - `--skip-post-init` - Skip npm install, git init and VSCode launch
 
 ---
+
 ## `pepr update`
 
 Update the current Pepr Module to the latest SDK version and update the global Pepr CLI to the same version.
@@ -23,12 +24,15 @@ Update the current Pepr Module to the latest SDK version and update the global P
 
 ## `pepr dev`
 
-Connect a local cluster to a local version of the Pepr Controller to do real-time debugging of your module.
+Connect a local cluster to a local version of the Pepr Controller to do real-time debugging of your module. Note
+the `pepr dev` assumes a K3d cluster is running by default. If you are working with Kind or another docker-based
+K8s distro, you will need to pass the `--host host.docker.internal` option to `pepr dev`. If working with a remote
+cluster you will have to give Pepr a host path to your machine that is reachable from the K8s cluster.
 
 **Options:**
 
 - `-l, --log-level [level]` - Log level: debug, info, warn, error (default: "info")
-- `-h, --host [host]` - Host to listen on (default: "host.docker.internal")
+- `-h, --host [host]` - Host to listen on (default: "host.k3d.internal")
 - `--confirm` - Skip confirmation prompt
 
 ---

package/docs/module.md

@@ -23,6 +23,7 @@ Each Pepr Module is it's own Typescript project, produced by [`pepr init`](./cli
    npm run k3d-setup
 
    # Launch pepr dev mode (npm start or pepr dev)
+   # If using another local K8s distro instead of k3d, use `pepr dev --host host.docker.internal`
    pepr dev
 
    # From another terminal, apply the sample yaml

package/osv-scanner.toml

@@ -0,0 +1,4 @@
+# One entry for each vulnerability group
+[[IgnoredVulns]]
+id = "GHSA-p8p7-x288-28g6"
+reason = "Library only used client-side and not affected by this vulnerability."

package/package.json

@@ -9,7 +9,7 @@
   "engines": {
     "node": ">=18.0.0"
   },
-  "version": "0.2.8",
+  "version": "0.2.9",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "pepr": {
@@ -67,7 +67,7 @@
     "@typescript-eslint/parser": "5.59.0",
     "ava": "5.2.0",
     "eslint": "8.39.0",
-    "nock": "13.3.0"
+    "nock": "13.3.1"
   },
   "ava": {
     "extensions": [