docs(templates): rename http-*-service-hono templates to http-*-handler-hono#632
Merged
ricochet merged 2 commits intowasmCloud:mainfrom Apr 29, 2026
Merged
Conversation
…er-hono
The "service" suffix collides with wasmCloud's defined notion of a
service: a long-running, stateful Wasm binary that acts as localhost
within a workload boundary. The HTTP-component templates affected here
are stateless components, not services. Rename them to "handler" to
better reflect their relationship to wasi:http/incoming-handler:
- templates/http-service-hono -> templates/http-handler-hono
- templates/http-blobstore-service-hono -> templates/http-blobstore-handler-hono
- templates/http-filesystem-service-hono -> templates/http-filesystem-handler-hono
- templates/http-kv-service-hono -> templates/http-kv-handler-hono
- templates/http-logging-service-hono -> templates/http-logging-handler-hono
Updates package.json names and build script outputs, .wash/config.yaml
component_path entries, WIT world names and .wasm output filenames,
README headers and prose, the root README and templates/README, plus
prose mentions ("HTTP service" -> "HTTP handler" where the prose refers
to the component itself).
The service-tcp-echo template keeps its name; it is an actual wasmCloud
service.
Also fixes a pre-existing typo in the logging template's WIT world name
(it was typescript-http-kv-service-hono, now typescript-http-logging-handler-hono).
A matching docs PR will land in wasmCloud/wasmcloud.com to update the
documentation references.
Signed-off-by: Eric Gregory <eric@cosmonic.com>
Following the http-*-service-hono → http-*-handler-hono rename, update the hardcoded API metadata strings in template source so the running component's JSON responses match the template's name: - http-handler-hono: "Hono HTTP Service" → "Hono HTTP Handler"; "comprehensive HTTP service" → "comprehensive HTTP handler" - http-blobstore-handler-hono: "Hono HTTP Blobstore Service" → "Hono HTTP Blobstore Handler" - http-kv-handler-hono: same description tweak - http-logging-handler-hono: "HTTP Logging Service" → "HTTP Logging Handler"; "A Hono service on wasmCloud" → "A Hono handler on wasmCloud" Also fixes the http-kv-handler-hono package-lock.json, which still had "name": "http-handler-hono" from a copy-paste — npm install during verification regenerated the correct name. Verified all five renamed templates run end-to-end under wash dev. Signed-off-by: Eric Gregory <eric@cosmonic.com>
ricochet
approved these changes
Apr 29, 2026
ericgregory
added a commit
to wasmCloud/wasmcloud.com
that referenced
this pull request
May 4, 2026
…ler-hono Tracks the template renames in wasmCloud/typescript#632: http-service-hono becomes http-handler-hono and the same suffix change applies to the blobstore, filesystem, kv, and logging variants. The "service" suffix collided with wasmCloud's defined notion of a service (a long-running, stateful Wasm binary), and these are stateless HTTP-handler components. "handler" matches the WIT export name (wasi:http/incoming-handler). Updated: - Template paths in docs/examples.mdx (table, anchors, source links, wash new --subfolder commands), and prose ("HTTP Service component" -> "HTTP Handler component") - TypeScript interface guides (configuration, blob-storage, key-value-storage, index): template paths, world names, build output filenames, and the "HTTP service project" prose mention The existing TCP echo example keeps its "service" wording because it truly is a wasmCloud service. Signed-off-by: Eric Gregory <eric@cosmonic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
servicesuffix is likely to create confusion with wasmCloud's defined notion of a service (a long-running, stateful Wasm binary). This PR renames templates that are stateless HTTP-handler components:templates/http-service-hono→templates/http-handler-honotemplates/http-blobstore-service-hono→templates/http-blobstore-handler-honotemplates/http-filesystem-service-hono→templates/http-filesystem-handler-honotemplates/http-kv-service-hono→templates/http-kv-handler-honotemplates/http-logging-service-hono→templates/http-logging-handler-honoservice-tcp-echokeeps its name, since it is an actual wasmCloud service.Coordinates with wasmCloud/wasmCloud#5084 (Rust template renames) and wasmCloud/wasmcloud.com#1138