kazaam
Task
kazaam | Task | |
---|---|---|
- | 122 | |
283 | 12,014 | |
2.5% | 3.9% | |
0.0 | 9.5 | |
over 2 years ago | 7 days ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kazaam
We haven't tracked posts mentioning kazaam yet.
Tracking mentions began in Dec 2020.
Task
-
Just: Just a Command Runner
I recently looked at various alternatives to make and landed on https://taskfile.dev/
It handles dependencies and conditions well without needing to be a full blown bash expert.
-
Mise: Dev tools, env vars, task runner
Have enjoyed replacing makefiles with https://taskfile.dev/ which looks like it could be more powerful due to being able to detect changes etc. But glad Just has been good.
-
Why I Switched from Makefile to Taskfile
Taskfile is a Go-based task runner using YAML syntax for defining tasks. It simplifies project workflows by automating repetitive tasks like building, testing, and deploying code.
-
I Like Makefiles
I also use make this way and have done for years. I even have the same kind of religious ritual the author has, like writing the Makefile is part of setting up the codebase and organising in my own head how the whole local dev environment is going to work.
The only thing is, this isn't what make is actually for. A number of commenters have recommended Just - the one I've been using on my personal projects is Task - https://taskfile.dev/ - which is pretty great. As other commenters have said, the problem is that make is installed everywhere already. I would love to see a task runner become standard to the same extent, and will have a look at Just if that's the one people are using.
-
Makefiles for Web Work (2022)
I use https://taskfile.dev and I love it.
-
Ask HN: Best Tools for Monorepo?
We have a very similar setup (except s/Next.js/Remix) and went with npm workspaces + Task [1], and it's working really, really well so far. This is our second iteration of a monorepo (first one was a straight React SPA bundled with Vite instead of Remix).
We have a root Taskfile that references our JS and Go taskfiles and wraps / abstracts all tasks. It's good for dependency management and task orchestration (`task lint` will run lint in both JS and Go for example, and `task test` does the same).
TypeScript sharing between packages can be a lil' funky, but so far it's super solid. Happy to share more if it would be helpful.
[1]: https://taskfile.dev/
-
Streamlining Project Automation with Makim
Taskfile is described as a task runner/build tool that aims to be simpler and easier to use. It is often used in the Go language.
-
Show HN: Bin CLI – A simple task/script runner for any programming language
Most projects I've worked on included a bunch of scripts for common tasks (installing dependencies, starting/stopping dev servers, testing and deploying changes, and so on). There are a few tools designed for this, such as Just (https://just.systems/) and Task (https://taskfile.dev/), and I know some people use Make as a task runner (e.g. https://news.ycombinator.com/item?id=40333481), but I've always preferred the simplicity and universality of shell scripts.
Bin CLI is a tool I wrote to add some of the niceties of these tools to shell scripts: it works even when you're currently in a subdirectory, only requires you to type enough of the command (script) name to uniquely identify it, and allows aliases to be defined. It also allows a project's commands to be listed (along with some help text), supports subcommands, and supports tab completion of command names. Of course scripts can be written in other languages too, just by adding the appropriate shebang.
Collaborators/contributors who don't have Bin CLI installed can just run the scripts directly - so I can enjoy the benefits without adding a hard dependency or extra barrier to entry. However, I also added support for defining one-liner scripts/aliases in a config file (much like "npm run" scripts are defined in package.json) for times when I want to avoid creating many trivial/wrapper scripts for common tasks.
It is implemented as a single Bash script, with minimal dependencies, small enough to keep in my Dotfiles repo (62 KB). I also made .deb and .rpm packages so it can easily be installed system-wide.
-
Alternatives to Makefiles written in Go
The first tool we will test is Taskfile, found on the website https://taskfile.dev/. The tool's idea is to perform tasks described in a file called Taskfile.yaml and, as the name suggests, in yaml.
-
Show HN: Workflow Orchestrator in Golang
So many tools in this space! This one looks a little bit like go-task, but it seems maybe better for production workflows because if timeout support, while go-task seems more aimed to command line work/makefile replacement.
—-
https://github.com/go-task/task
What are some alternatives?
fastlz - Wrap over FastLz for GoLang
just - 🤖 Just a command runner
xlsx - Go library for reading and writing XLSX files.
goreleaser - Release engineering, simplified
pm - Processlist manager with TCP listener
dagger - An engine to run your pipelines in containers
peco - Simplistic interactive filtering tool
doit - CLI task management & automation tool
fzf - :cherry_blossom: A command-line fuzzy finder
JobRunner - Framework for performing work asynchronously, outside of the request flow
go-bind-plugin - go-bind-plugin generates API for exported plugin symbols (-buildmode=plugin) - go1.8+ only (http://golang.org/pkg/plugin)
Bazel - a fast, scalable, multi-language and extensible build system