render-workflows-dart 0.8.2 → 0.8.3

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.8.3
+
+Documentation only, but it needs a release: npm serves a README from the
+archive, so 0.8.2's registry page still taught `render-dart build`.
+
+Every command in the docs, in the example `npm` scripts, and in the build's own
+log lines now reads `render-workflows-dart`. One name to learn, and it is the
+one you install. `render-dart` remains a second bin, documented as an alias, so
+nothing that already exists breaks.
+
 ## 0.8.2
 
 **Renamed to `render-workflows-dart`.** `render-dart` said neither which Render

package/README.md

@@ -1,8 +1,8 @@
 # render-workflows-dart
 
 > **Renamed.** This package was `render-dart` up to 0.8.1 and is
-> `render-workflows-dart` from 0.8.2. The `render-dart` command still works, so
-> an existing project only changes one line:
+> `render-workflows-dart` from 0.8.2. The old `render-dart` command still works
+> as an alias, so an existing project only changes one line:
 >
 > ```diff
 > -    "render-dart": "^0.8.1"
@@ -26,7 +26,7 @@ no built-in way to use Dart: tasks are defined with Render's own SDK, which is
 available for **TypeScript and Python** only. Their docs say SDKs for more
 languages are planned.
 
-`render-dart` provides first class dart language support, without reaching for Docker (which
+`render-workflows-dart` provides first class dart language support, without reaching for Docker (which
 would cost API provisioning and local development). It can compile Dart **two
 ways**:
 
@@ -48,7 +48,7 @@ access to render's apis (neither are required to use this one):
 
 | | |
 | --- | --- |
-| `render-dart` (this) | **Writing** tasks in Dart |
+| `render-workflows-dart` (this) | **Writing** tasks in Dart |
 | [`render_workflows`](https://pub.dev/packages/render_workflows) | **Running** workflows/tasks — start, watch, cancel, fan out |
 | [`render_api`](https://pub.dev/packages/render_api) | **Managing** the services — create, deploy, inspect |
 
@@ -91,7 +91,7 @@ template that does not work is a test failure rather than a surprise.
 ## Coding agents
 
 Agents never read `node_modules`, so nothing shipped inside this package
-reaches one helping in your project. `render-dart init` therefore writes an
+reaches one helping in your project. `render-workflows-dart init` therefore writes an
 `AGENTS.md` (and a `CLAUDE.md` pointing at it) **into the project it creates**,
 covering the traps, when to reach for a native task, and how to get at a
 database.
@@ -146,7 +146,7 @@ render workflows create --name my-workflow --repo <url> \
   --run-command "node index.js"
 ```
 
-No Dart is needed on Render's builder — `render-dart build` fetches a pinned
+No Dart is needed on Render's builder — `render-workflows-dart build` fetches a pinned
 SDK when none is present.
 
 > Blueprints (`render.yaml`) do not support Workflows, so provisioning is via
@@ -156,11 +156,11 @@ SDK when none is present.
 
 | | |
 | --- | --- |
-| `render-dart build` | Compile `tasks.dart` to `build/tasks.js`, skipping if fresh |
-| `render-dart dev` | Build, then start Render's local task server |
-| `render-dart init [dir] [--template <name>]` | Scaffold a new project from an [example](#examples-which-are-also-templates) |
-| `render-dart dart` | Which Dart this project will use, and why |
-| `render-dart dart --list` | Every version the archive offers |
+| `render-workflows-dart build` | Compile `tasks.dart` to `build/tasks.js`, skipping if fresh |
+| `render-workflows-dart dev` | Build, then start Render's local task server |
+| `render-workflows-dart init [dir] [--template <name>]` | Scaffold a new project from an [example](#examples-which-are-also-templates) |
+| `render-workflows-dart dart` | Which Dart this project will use, and why |
+| `render-workflows-dart dart --list` | Every version the archive offers |
 
 `--template` takes any directory name under
 [`examples/`](examples) — `default` (the default), `http`, `native`,
@@ -211,8 +211,8 @@ for varying a build without a commit — Render's dashboard sets those — and
 `package.json` for the answer that should travel with the project:
 
 ```bash
-npx render-dart build --dart-version 3.12.2
-RENDER_DART_VERSION=3.12.2 npx render-dart build
+npx render-workflows-dart build --dart-version 3.12.2
+RENDER_DART_VERSION=3.12.2 npx render-workflows-dart build
 ```
 
 ```json
@@ -225,8 +225,8 @@ keeps building when the archive is unreachable; an alias is resolved against
 the archive on each build, which is the point of asking for one.
 
 ```bash
-npx render-dart dart          # what this project will use, and why
-npx render-dart dart --list   # 176 stable releases, newest first
+npx render-workflows-dart dart          # what this project will use, and why
+npx render-workflows-dart dart --list   # 176 stable releases, newest first
 ```
 
 **A pin set explicitly wins over a Dart already on `PATH`.** If they differ, the
@@ -256,7 +256,7 @@ check happened.
 
 ## Using pub.dev packages
 
-Add them to `pubspec.yaml` as normal; `render-dart build` runs `dart pub get`
+Add them to `pubspec.yaml` as normal; `render-workflows-dart build` runs `dart pub get`
 for you. What works is determined by dart2js, not by Render:
 
 | | Works? | |
@@ -268,7 +268,7 @@ for you. What works is determined by dart2js, not by Render:
 **`dart:io` is the trap.** dart2js compiles it without complaint and then
 throws `Unsupported operation` at runtime — so a task using it deploys cleanly
 and fails on its first real run, potentially burning up to the task timeout
-first. `render-dart build` therefore refuses to build a project that imports
+first. `render-workflows-dart build` therefore refuses to build a project that imports
 `dart:io` directly, and tells you what to use instead. Conditional imports
 (`if (dart.library.io)`) are left alone, and `allowDartIo` opts out.
 
@@ -394,7 +394,7 @@ ranked.
 | Extra artefact | none | a binary, built during the deploy |
 
 **Reach for wasm when the package already has one.** `forge2d` and
-`rust_crypto` both do, and `render-dart` resolves their modules without
+`rust_crypto` both do, and `render-workflows-dart` resolves their modules without
 configuration. Nothing is spawned and nothing is compiled.
 
 **Reach for native when there is no wasm build, when the work needs I/O or
@@ -475,7 +475,7 @@ import 'native/tools.dart';
 task('inspect', (args) async => await inspect(args[0]! as String));
 ```
 
-`render-dart build` generates `native/tools.dart` as a conditional export:
+`render-workflows-dart build` generates `native/tools.dart` as a conditional export:
 
 ```dart
 export 'tools.stub.dart' if (dart.library.io) 'tools_impl.dart';

package/examples/README.md

@@ -23,7 +23,7 @@ reality; making them the same thing means every template is one you can run.
 ```bash
 cd http
 npm install
-npx render-dart dev
+npx render-workflows-dart dev
 ```
 
 Then, in another terminal:

package/examples/default/README.md

@@ -1,7 +1,7 @@
 # default
 
 The Workflows basics, with no dependencies beyond the SDK. This is what
-`render-dart init` produces with no `--template`.
+`render-workflows-dart init` produces with no `--template`.
 
 | Task | Shows |
 | --- | --- |
@@ -10,7 +10,7 @@ The Workflows basics, with no dependencies beyond the SDK. This is what
 | `flaky` | Retry policy, and a failure reaching Render with its real message |
 
 ```bash
-npm install && npx render-dart dev
+npm install && npx render-workflows-dart dev
 render workflows start sumSquares --local --input='[[2, 3, 4]]'   # 29
 ```
 

package/examples/default/index.js

@@ -1,2 +1,2 @@
 // Render runs this as the start command.
-require('render-dart/runtime').runTasks('./build/tasks.js');
+require('render-workflows-dart/runtime').runTasks('./build/tasks.js');

package/examples/default/package.json

@@ -3,13 +3,13 @@
   "version": "0.1.0",
   "private": true,
   "scripts": {
-    "build": "render-dart build",
+    "build": "render-workflows-dart build",
     "start": "node index.js",
-    "dev": "render-dart dev"
+    "dev": "render-workflows-dart dev"
   },
   "dependencies": {
     "@renderinc/sdk": "^0.6.0",
-    "render-dart": "^0.7.1"
+    "render-workflows-dart": "^0.8.2"
   },
   "engines": {
     "node": ">=18"

package/examples/http/README.md

@@ -14,7 +14,7 @@ why the build refuses a direct `dart:io` import.
 | `fetchMany` | Overlapping requests — I/O concurrency needs no extra cores |
 
 ```bash
-npm install && npx render-dart dev
+npm install && npx render-workflows-dart dev
 render workflows start fetchRepo --local --input='["dart-lang/sdk"]'
 ```
 

package/examples/http/index.js

@@ -1,2 +1,2 @@
 // Render runs this as the start command.
-require('render-dart/runtime').runTasks('./build/tasks.js');
+require('render-workflows-dart/runtime').runTasks('./build/tasks.js');

package/examples/http/package.json

@@ -4,13 +4,13 @@
   "private": true,
   "description": "Calling external APIs from a Render Workflows task written in Dart",
   "scripts": {
-    "build": "render-dart build",
+    "build": "render-workflows-dart build",
     "start": "node index.js",
-    "dev": "render-dart dev"
+    "dev": "render-workflows-dart dev"
   },
   "dependencies": {
     "@renderinc/sdk": "^0.6.0",
-    "render-dart": "^0.7.1"
+    "render-workflows-dart": "^0.8.2"
   },
   "engines": {
     "node": ">=18"

package/examples/introspect/README.md

@@ -14,7 +14,7 @@ networking.
 | `runElsewhere` | Starting a task in another workflow and waiting for it |
 
 ```bash
-npm install && npx render-dart dev
+npm install && npx render-workflows-dart dev
 render workflows start auditDatabases --local --input='[]'
 render workflows start runElsewhere --local \
   --input='["some-workflow/someTask", [7]]'

package/examples/introspect/index.js

@@ -1,2 +1,2 @@
 // Render runs this as the start command.
-require('render-dart/runtime').runTasks('./build/tasks.js');
+require('render-workflows-dart/runtime').runTasks('./build/tasks.js');

package/examples/introspect/package.json

@@ -4,13 +4,13 @@
   "private": true,
   "description": "A Render Workflows task that uses Render's own API and Workflows SDKs",
   "scripts": {
-    "build": "render-dart build",
+    "build": "render-workflows-dart build",
     "start": "node index.js",
-    "dev": "render-dart dev"
+    "dev": "render-workflows-dart dev"
   },
   "dependencies": {
     "@renderinc/sdk": "^0.6.0",
-    "render-dart": "^0.7.1"
+    "render-workflows-dart": "^0.8.2"
   },
   "engines": {
     "node": ">=18"

package/examples/native/README.md

@@ -14,7 +14,7 @@ nothing at the call site says it is native.
 | `parallelHash` | Isolates across cores, timed against the sequential version |
 
 ```bash
-npm install && npx render-dart dev
+npm install && npx render-workflows-dart dev
 render workflows start parallelHash --local --input='[["a","b","c","d","e","f","g","h"]]'
 ```
 

package/examples/native/index.js

@@ -1,2 +1,2 @@
 // Render runs this as the start command.
-require('render-dart/runtime').runTasks('./build/tasks.js');
+require('render-workflows-dart/runtime').runTasks('./build/tasks.js');

package/examples/native/package.json

@@ -4,13 +4,13 @@
   "private": true,
   "description": "dart:io, dart:ffi and parallel isolates from a Render Workflows task",
   "scripts": {
-    "build": "render-dart build",
+    "build": "render-workflows-dart build",
     "start": "node index.js",
-    "dev": "render-dart dev"
+    "dev": "render-workflows-dart dev"
   },
   "dependencies": {
     "@renderinc/sdk": "^0.6.0",
-    "render-dart": "^0.7.1"
+    "render-workflows-dart": "^0.8.2"
   },
   "renderDart": {
     "native": [

package/examples/postgres/README.md

@@ -34,7 +34,7 @@ dart pub get && dart run bin/seed.dart
 
 cd ..
 export DATABASE_URL=<external connection string>
-npm install && npx render-dart dev
+npm install && npx render-workflows-dart dev
 render workflows start widgetStats --local --input='[]'
 ```
 

package/examples/postgres/index.js

@@ -1,2 +1,2 @@
 // Render runs this as the start command.
-require('render-dart/runtime').runTasks('./build/tasks.js');
+require('render-workflows-dart/runtime').runTasks('./build/tasks.js');

package/examples/postgres/package.json

@@ -4,13 +4,13 @@
   "private": true,
   "description": "Reading and writing Render Postgres from a Dart workflow task",
   "scripts": {
-    "build": "render-dart build",
+    "build": "render-workflows-dart build",
     "start": "node index.js",
-    "dev": "render-dart dev"
+    "dev": "render-workflows-dart dev"
   },
   "dependencies": {
     "@renderinc/sdk": "^0.6.0",
-    "render-dart": "^0.7.1"
+    "render-workflows-dart": "^0.8.2"
   },
   "renderDart": {
     "native": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "render-workflows-dart",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "description": "Unofficial: write Render Workflows tasks in Dart, compiled to JavaScript. Not affiliated with or endorsed by Render.",
   "license": "MIT",
   "repository": {

package/runtime/AGENTS.md

@@ -1,7 +1,7 @@
 # Working in this project
 
 Render Workflows tasks written in Dart, built by
-[`render-dart`](https://github.com/timmaffett/render_workflows_dart).
+[`render-workflows-dart`](https://github.com/timmaffett/render_workflows_dart).
 
 Task bodies are compiled to JavaScript with `dart compile js` and registered
 through Render's official `@renderinc/sdk` on the `node` runtime. Where
@@ -10,16 +10,16 @@ JavaScript is not enough, a task calls into Dart compiled natively.
 ## Commands
 
 ```bash
-npx render-dart build         # compile; --force skips the freshness check
-npx render-dart dev           # build, then start Render's local task server
-npx render-dart dart          # which Dart this project uses, and why
+npx render-workflows-dart build         # compile; --force skips the freshness check
+npx render-workflows-dart dev           # build, then start Render's local task server
+npx render-workflows-dart dart          # which Dart this project uses, and why
 render workflows tasks list --local
 render workflows start <task> --local --input='[1, 2]'
 ```
 
 No Dart installation is needed. If one is on `PATH` the build uses it;
 otherwise an SDK is fetched into `node_modules`. Either way the build prints
-which version it used and where it came from, so `render-dart dart` is only
+which version it used and where it came from, so `render-workflows-dart dart` is only
 needed before building.
 
 To pin a version, put it in `package.json` — that is the form that travels
@@ -106,7 +106,7 @@ single-threaded.
 pub.dev marks it `runtime:native-aot` with no `runtime:web`. So a database
 needs a native task, holding the connection open with `worker: true`.
 
-`render-dart init db --template postgres` scaffolds a working version, seeder
+`render-workflows-dart init db --template postgres` scaffolds a working version, seeder
 included.
 
 The connection string belongs in `DATABASE_URL` on the service, set to the

package/src/cli.js

@@ -18,9 +18,9 @@ const { compile, findDartIoImports, isFresh, pubGet } = require('./toolchain/com
 const { nativeEntries, buildNative, writeGeneratedIgnores } = require('./toolchain/native');
 const { generate, ensureRuntimeFile } = require('./toolchain/generate');
 
-const log = (m) => console.log(`[render-dart] ${m}`);
+const log = (m) => console.log(`[render-workflows-dart] ${m}`);
 const fail = (m) => {
-  console.error(`[render-dart] ${m}`);
+  console.error(`[render-workflows-dart] ${m}`);
   process.exit(1);
 };
 

package/src/runtime.js

@@ -89,7 +89,7 @@ globalThis.__callTask = (name, args) => {
  */
 globalThis.__start = () =>
   startTaskServer().catch((e) => {
-    console.error('[render-dart] task failed:', e && e.message ? e.message : e);
+    console.error('[render-workflows-dart] task failed:', e && e.message ? e.message : e);
     process.exit(1);
   });