Repository navigation
feat: add script-only JSON pipeline example - #2349
Merged
Merged
Conversation
vados-cosmonic
force-pushed
the
example/script-only-pipeline
branch
from
October 29, 2026 15:30
30ca788 to
43ca9b7
Compare
vados-cosmonic
force-pushed
the
example/script-only-pipeline
branch
from
October 29, 2026 16:24
c7d9c8e to
2f199b5
Compare
vados-cosmonic
enabled auto-merge
October 29, 2026 16:24
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
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.
Adds an access-log processing example in which TypeScript script-only components share one QuickJS engine and an in-engine dataset. The same pipeline runner and runtime component loader run in Node.js and the browser.
The browser starts with an empty pipeline and accepts uploaded
.wasmprocessing components. Users can filter synthetic GeoIP locations, calculate risk scores, count page visits, edit options, and reorder or remove steps. Each run resets the input while retaining the engine instance.Includes generated WIT interface types, separate component and demo directories, a walkthrough README, conventional example scripts, workspace registration, and CI coverage.