Skip to content

helloworld project sample for Typescript#344

Draft
THardy98 wants to merge 8 commits into
mainfrom
feat/ts-hello-world
Draft

helloworld project sample for Typescript#344
THardy98 wants to merge 8 commits into
mainfrom
feat/ts-hello-world

Conversation

@THardy98
Copy link
Copy Markdown
Contributor

@THardy98 THardy98 commented May 1, 2026

What was changed

Add a helloworld project sample for the Typescript harness

Why?

Showcase, reference sample

  1. How was this tested:
    Added to test suite and CI

@THardy98 THardy98 changed the title Feat/ts hello world helloworld project sample for Typescript May 1, 2026
@THardy98 THardy98 force-pushed the feat/ts-hello-world branch from 0957c31 to c9d8804 Compare May 11, 2026 13:58
THardy98 added 6 commits May 11, 2026 11:48
  Project images now use the same prepared directory name for worker and scenario
  runtime paths. The Dockerfiles only conditionally add --project-name, while the
  shared entrypoint derives the project prebuilt path instead of carrying separate
  project-specific env vars.

TypeScript project builds install and build workspace dependencies first, then
  run sdkbuild from the project fixture directory with an absolute file: harness
  dependency. CI also stops adding a Python-only v prefix to SDK versions
Root TS workspace runs root proto-gen before harness build. Removed the `prepare` script during harness install.
Check that both the JS and TS output exist when checking protogen
@THardy98 THardy98 force-pushed the feat/ts-hello-world branch from 213fa51 to 6121a0c Compare May 11, 2026 15:48
@THardy98 THardy98 force-pushed the feat/ts-hello-world branch from 3f59ad0 to f315b9d Compare May 11, 2026 17:01
…which fails when go walks the tree for ./...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant