Conversation
The typescript-app quickstart already uses the ts-loader approach for TypeScript runtime actions, but the README only mentioned TypeScript for UI components. This was causing confusion — people thought the example used manual tsc compilation with duplicated source directories. Changes: - Rewrite README to document the ts-loader setup for runtime actions, including webpack config, tsconfig, and app.config.yaml usage - Remove unnecessary output.filename from webpack-config.js (App Builder overrides this as an immutable option) - Clean up tsAction/index.ts: fix the function signature to match the actual Runtime action contract, remove unused variable and type Made-with: Cursor
pru55e11
pushed a commit
to AdobeDocs/app-builder
that referenced
this pull request
Mar 26, 2026
Remove the caveat about the quickstart using a manual tsc approach, since adobe/appbuilder-quickstarts#15 updates the example to properly document the ts-loader method. Made-with: Cursor
1 task
purplecabbage
approved these changes
Mar 26, 2026
pru55e11
added a commit
to AdobeDocs/app-builder
that referenced
this pull request
Mar 26, 2026
… up (#522) Remove the caveat about the quickstart using a manual tsc approach, since adobe/appbuilder-quickstarts#15 updates the example to properly document the ts-loader method.
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.
Summary
The
typescript-appquickstart already uses thets-loaderWebpack approach for TypeScript runtime actions, but the README only documented TypeScript for UI components (.tsx). This caused confusion — it looked like TypeScript actions required manualtsccompilation with duplicated source directories.ts-loadersetup for runtime actions (webpack config, tsconfig,app.config.yamlpointing to.tsfiles), alongside the existing UI TypeScript guidanceoutput.filenamefromwebpack-config.js— App Builder overrides this as an immutable option, so including it was misleadingtsAction/index.ts— fixed the function signature to match the actual Runtime action contract (singleparamsargument), removed unused variable and typeContext
This was identified during work on AdobeDocs/app-builder#521, which adds TypeScript runtime actions documentation to the public docs. A reviewer noted that linking to this quickstart was confusing because the README didn't explain the TypeScript action setup.
Original discussion: #app-builder Slack thread
Test plan
aio app buildsucceeds with the updatedwebpack-config.js(nooutput.filename)tsActionbuilds and deploys correctly with the cleaned-upindex.tsMade with Cursor