Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deno task: support empty command if dependencies are specified #27165

Open
lowlighter opened this issue Nov 30, 2024 · 0 comments · May be fixed by #27191
Open

deno task: support empty command if dependencies are specified #27165

lowlighter opened this issue Nov 30, 2024 · 0 comments · May be fixed by #27191
Assignees
Labels
suggestion suggestions for new features (yet to be agreed) task runner related to deno task

Comments

@lowlighter
Copy link
Contributor

Version: Deno 2.1.2

If dependencies are specified within a task, it'd be nice to not be required to specify a command (basically creating an alias for multiple commands).

{
  "tasks": {
    "build": {
      "dependencies": ["build:a", "build:b"]
    },
    "build:a": "...",
    "build:b": "..."
  }
}

This is kind of separate from #26944, because the wildcard may catch too much tasks

@marvinhagemeister marvinhagemeister self-assigned this Nov 30, 2024
marvinhagemeister added a commit to denoland/deno_config that referenced this issue Dec 2, 2024
Make the task's `command` property optional. There are valid reasons to
have a task that has no command, but task dependencies. This is often
used to group tasks.

See denoland/deno#27165
@bartlomieju bartlomieju added suggestion suggestions for new features (yet to be agreed) task runner related to deno task labels Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion suggestions for new features (yet to be agreed) task runner related to deno task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants