feat: ability to provide JavaScript objects and streams as file descriptors for redirects #230
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.
This adds to Dax what's available in Bun's shell where instead of providing objects to the entire command like so:
You can now do:
You can also now redirect into any
WritableStream
:Or do an input redirect from any
ReadableStream
:Or provide bytes:
Or
Response
objects:Other supported objects:
FsFileWrapper
(dax's wrapper over Deno'sFsFile
in the$.path
API)Function
- Must return aReadableStream<Uint8Array>
orWritableStream
Additionally, the
$.symbols.writable
(Symbol.for("dax.writableStream")
) and$.symbols.readable
(Symbol.for("dax.readableStream")
) symbols can be attached to any object to make them work in these positions (still debating this).Unsupported objects in this position will cause an error: