deno_task_shell
deno_task_shell copied to clipboard
denoland
Cross platform shell for deno task.
I have this in my deno.json ``` { "tasks": { "check": "deno check services/*/{prod,dev}.ts" } ``` When I run `deno task check`, I got: ``` Task check deno check services/*/{prod,dev}.ts...
Historically, looping has been pretty handy. Simple support is wanted to avoid lengthier JavaScripts: ```sh $ for i in a b c; do echo 1 $i 2; done 1 a...
I'd like the task shell to be able to use grep. In the olden days, using Node, shelljs provided grep and sed, very useful. https://github.com/shelljs/shelljs
The `xargs` command is super useful but is too constrained to use for invocations that depend on positional parameters. This feature request asks for [the traditional -I/-i/--replace flags](https://man7.org/linux/man-pages/man1/xargs.1p.html#OPTIONS) to be...
## Version ```console $ deno --version deno 1.40.1 (release, x86_64-unknown-linux-gnu) v8 12.1.285.6 typescript 5.3.3 ``` ## Step to reproduce deno.jsonc ```jsonc { "tasks": { "test-head": "head -n -1 test.txt" }...
To make it easier to perform op depending on paths
I'm migrating to using pixi tasks to run various python-related scripts. Most of these generate some output that the user typically wants to open in the default application on their...
* https://github.com/harryfei/which-rs/pull/109
For example: ``` echo for ``` should be allowed instead of erroring.
A user of `pixi` reported that piping stdin into `deno_task_shell` has an issue (https://github.com/prefix-dev/pixi/issues/3462) I created the folling reproducer: ```rust use std::env; use std::collections::HashMap; use anyhow::{Context, Result}; use tokio; #[tokio::main]...
