@pikku/queue-nats 0.12.2 → 0.12.4

package/dist/nats-scheduler-service.js

@@ -9,7 +9,7 @@ import { SCHEDULE_HEADER, SCHEDULE_TARGET_HEADER, SCHEDULE_TIMEZONE_HEADER, SCHE
 /**
  * Queue recurring cron fires land on.
  *
- * Deliberately separate from `pikku-remote-internal-rpc` (where one-off
+ * Deliberately separate from `pikku-mesh-rpc` (where one-off
  * `scheduleRPC` calls land): that queue is a registered pikku worker whose
  * consumer is owned by the queue registry, and a recurring task is not an RPC
  * invocation — it goes through `runScheduledTask`, which resolves the task's
@@ -18,7 +18,7 @@ import { SCHEDULE_HEADER, SCHEDULE_TARGET_HEADER, SCHEDULE_TIMEZONE_HEADER, SCHE
  */
 const RECURRING_TASK_QUEUE = 'pikku-recurring-scheduled-task';
 /** Queue a one-off `scheduleRPC` fires onto — a registered pikku worker. */
-const REMOTE_RPC_QUEUE = 'pikku-remote-internal-rpc';
+const MESH_RPC_QUEUE = 'pikku-mesh-rpc';
 /** Concurrent in-flight scheduled tasks. */
 const RECURRING_MAX_ACK_PENDING = 5;
 /** Ack window for a recurring fire. Generous: recurring tasks are batch
@@ -125,12 +125,12 @@ export class NatsSchedulerService extends SchedulerService {
      */
     async scheduleRPC(delay, rpcName, data, session) {
         const delayMs = typeof delay === 'string' ? parseDurationString(delay) : delay;
-        const subject = scheduleSubjectFor(this.subjectPrefix, REMOTE_RPC_QUEUE);
+        const subject = scheduleSubjectFor(this.subjectPrefix, MESH_RPC_QUEUE);
         const hdrs = headers();
         // A timestamp already in the past fires immediately rather than erroring,
         // which matches pg-boss's `startAfter` with an elapsed date.
         hdrs.set(SCHEDULE_HEADER, `@at ${new Date(Date.now() + delayMs).toISOString()}`);
-        hdrs.set(SCHEDULE_TARGET_HEADER, subjectForQueue(this.subjectPrefix, REMOTE_RPC_QUEUE));
+        hdrs.set(SCHEDULE_TARGET_HEADER, subjectForQueue(this.subjectPrefix, MESH_RPC_QUEUE));
         await this.js.publish(subject, JSON.stringify({ rpcName, data, session }), { headers: hdrs });
         return subject;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pikku/queue-nats",
-  "version": "0.12.2",
+  "version": "0.12.4",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/pikkujs/pikku.git",
@@ -17,12 +17,13 @@
     "test": "bash run-tests.sh",
     "test:coverage": "bash run-tests.sh --coverage",
     "ncu": "npx npm-check-updates",
-    "build": "tsc -b",
+    "build": "bun run clean && tsc -b",
     "release": "npm run build && npm test",
-    "prepublishOnly": "bun run build"
+    "prepublishOnly": "bun run build",
+    "clean": "rm -rf dist tsconfig.tsbuildinfo"
   },
   "peerDependencies": {
-    "@pikku/core": "^0.12.108"
+    "@pikku/core": "^0.12.146"
   },
   "dependencies": {
     "@nats-io/jetstream": "^3.4.0",
@@ -30,6 +31,11 @@
     "@nats-io/transport-node": "^3.4.0"
   },
   "exports": {
-    ".": "./dist/index.js"
-  }
+    ".": "./dist/index.js",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist",
+    "!dist/**/*.tsbuildinfo"
+  ]
 }

package/CHANGELOG.md

@@ -1,37 +0,0 @@
-# @pikku/queue-nats
-
-## 0.12.2
-
-### Patch Changes
-
-- 4c7a1b5: Run the monorepo's own scripts through bun instead of yarn. What moves is the
-  package manager each package's `prepublishOnly` and build scripts invoke, plus
-  the two manifest fixes bun needs to resolve the tree: `uWebSockets.js` is
-  declared with an explicit `github:` specifier, and `@pikku/uws-handler` marks
-  its `uWebSockets.js` peer optional so a bun install of a consumer that brings
-  its own uWS app does not try to fetch it from the registry.
-
-  Three published behaviours change, all of them cases where an isolated
-  `node_modules` or bun as the runtime had been papered over by yarn's hoisting:
-
-  - `@pikku/migrator-sql` turns foreign keys on when it opens a sqlite database
-    through bun. `node:sqlite` enforces them by default and `bun:sqlite` does not,
-    which silently turned every `ON DELETE CASCADE` into a no-op under
-    `bunx --bun pikku`.
-  - `@pikku/cli` resolves a deploy provider against the project being deployed
-    rather than against wherever the CLI itself is installed, which is what its
-    own "is not installed" error asks the user to arrange.
-  - `@pikku/cli` treats a specifier a runtime hands straight back — bun does this
-    for the modules it implements itself — as not resolved from the project, so
-    it falls back rather than loading the runtime's own copy.
-
-- Updated dependencies [4c7a1b5]
-  - @pikku/core@0.12.108
-
-## 0.12.1
-
-### Patch Changes
-
-- 427c4fe: **`@pikku/queue-nats`** — NATS JetStream queue, worker and scheduler services, alongside the pg-boss and bullmq adapters. Jobs publish to a work-queue stream, each queue gets its own durable pull consumer, and `max_ack_pending` is real per-message concurrency rather than a batch size, so a slow job occupies one slot instead of holding its batch siblings. The per-job retry policy travels in headers because JetStream's `max_deliver` is per-consumer and cannot express a step marked "never retry", and `ack_wait` is always set to pg-boss's 900s parity rather than left to the server's 30s default — unset, any job running longer than 30s is redelivered while it is still running and executed twice. Cron and one-shot delays use the server's own message scheduler, so a schedule is a retained message on a reserved subject: publishing registers it, republishing replaces it, purging cancels it. That needs a server on 2.14+, and `NatsServiceFactory` refuses to start against anything older rather than silently not scheduling. `supportsResults` is `false`, deliberately — a work-queue stream deletes a message on ack, so there is nowhere for a job result or any job history to live, and per-job outcomes come from telemetry instead.
-- Updated dependencies [1ab831e]
-  - @pikku/core@0.12.105

package/run-tests.sh

@@ -1,68 +0,0 @@
-#!/bin/bash
-
-# Enable nullglob to handle cases where no files match the pattern
-shopt -s nullglob
-
-# Initialize variables for options
-watch_mode=false
-coverage_mode=false
-
-# Parse command-line options
-while [[ $# -gt 0 ]]; do
-  case $1 in
-    --watch)
-      watch_mode=true
-      shift
-      ;;
-    --coverage)
-      coverage_mode=true
-      shift
-      ;;
-    *)
-      echo "Unknown option: $1"
-      exit 1
-      ;;
-  esac
-done
-
-# Define the pattern to match your test files
-pattern="src/*.test.ts"
-
-# Expand the pattern into an array of files
-files=($(find src -type f -name "*.test.ts"))
-
-# Check if any files matched the pattern
-if [ ${#files[@]} -eq 0 ]; then
-  echo "No test files found matching pattern: $pattern"
-  if [ "${STRICT_TEST_DISCOVERY}" = "1" ]; then
-    exit 1
-  fi
-  exit 0
-fi
-
-# Construct the bun command
-#
-# --parallel gives every test file its own worker process, which is what node's
-# `--test` did. Several suites keep module-level caches (a TypeScript program, a
-# temp fixture directory) that a shared process would leak between files.
-#
-# --timeout because bun caps a test at 5s by default where node had no cap, and
-# the suites that build real TypeScript programs run well past that.
-bun_cmd=(bun test --parallel --timeout 120000)
-
-# Append options based on flags
-if [ "$watch_mode" = true ]; then
-  # --watch reruns in one process; parallel workers have nothing to watch.
-  bun_cmd=(bun test --watch --timeout 120000)
-fi
-
-if [ "$coverage_mode" = true ]; then
-  # --coverage-dir=. keeps lcov.info at the package root: CI merges every
-  # package's report by prefixing its SF paths with the file's own directory,
-  # so a nested coverage/ directory would re-root them one level too deep.
-  bun_cmd+=(--coverage --coverage-reporter=lcov --coverage-reporter=text --coverage-dir=.)
-  export PIKKU_TEST_COVERAGE=1
-fi
-
-# Execute the bun command with the expanded list of files
-"${bun_cmd[@]}" "${files[@]}"