scripts-to-rule-them-all
confgen
scripts-to-rule-them-all | confgen | |
---|---|---|
8 | 3 | |
3,140 | 2 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | over 1 year ago | |
Shell | TypeScript | |
Creative Commons Zero v1.0 Universal | - |
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.
scripts-to-rule-them-all
-
What’s with DevOps engineers using `make` of all things?
Personally I like https://github.blog/2015-06-30-scripts-to-rule-them-all/ as a pattern and then let the authors do whatever crazy thing they want from there. In my experience, 99% of repos never move past using simple shell scripts with a few common functions with that pattern, and things are kept fairly simple. A select few repositories tend to mature enough that they are able to invest in swapping towards something more testable than shell scripts, and then you just have a couple people who stick to invoking `make` from the scripts but it's fine and nobody has to think about it except them. We don't stick to that exact set of scripts, but find that as long as you don't use more than like 10ish entrypoints in `script/*`, and have at least `script/bootstrap` it's fine.
- Scripts to Rule Them All (2015)
-
Just: A Command Runner
I dig the general idea, but question the value add over a directory of `scripts` that follow sane conventions (ie `script/test`, `script/build` etc). Is the main thing that you can do `just -l` to see available commands? I have never really reached for `make` when I've had a choice, as I've done mostly ruby, JS, or java where you have more sane, humane tools (i.e. Rake, Yarn, Maven though that one is never fun).
My general approach is every repo should have something that follows https://github.com/github/scripts-to-rule-them-all, written in sh (maybe bash, its 2023), linted with shellcheck. When you need something fancy Rake is great or grab some nice bash command line helper and source it from all your scripts. Is a command listing really worth another dependency over what you get from `ls script` or `cat script/README` ?
- [AskJS] What is the best way to create a common npm package for building others?
-
Azure Pipeline running task in background?
Afaik AzDo cannot run tasks concurrently. From having had to work with azure pipelines I would highly suggest to use the github approach of Scripts to rule them all and avoiding predefined tasks unless absolutely necessary(Things that are complicated to implement and solutions already existing.
-
Why is uncoupled documentation bad?
GitHub have a pattern for this called "scripts to rule them all" - https://github.com/github/scripts-to-rule-them-all - I've not fully adopted it yet but I probably should, it looks very well thought-out.
-
Script up your projects
People at Github made an attempt to fix this situation: scripts to rule them all. The idea is to have common set of executable scripts for common developer tasks in a script/ directory in the root of every project:
-
How to Join a Team and Learn a Codebase
https://github.com/github/scripts-to-rule-them-all
confgen
-
JavaScript Gom Jabbar
FWIW, I have a side project, confgen https://github.com/erikpukinskis/confgen, which tries to help with this.
Assuming it’s an app (and not a library) get what you are describing you would run:
npx confgen@latest @app vite typescript eslint prettier react
-
The Node ecosystem (still) has tooling problems
It’s still early days, but I have been working on this…
There are scaffolding tools that help configure all the JavaScript frontend stuff you need, but the problem is you run them once and you can’t ever run them again to change/add stuff.
So I built Confgen which is sort of like create-react-app except it’s idempotent:
https://github.com/erikpukinskis/confgen
It’s very alpha, but I would love to get ideas/ bug reports on GitHub.
It’s also currently Vite-only, but I’m open to a possible webpack/babel mode in the future.
-
[AskJS] What is the best way to create a common npm package for building others?
I made my own for exactly the reasons you cite: https://github.com/erikpukinskis/confgen but it’s extremely opinionated and very alpha. Basically, if you are working in the cluster of Vite, TypeScript, Apollo, etc it will work but it doesn’t work with anything else.
What are some alternatives?
govuk_design_system_formbuild
generate-package - Use as a sub-generator or plugin in your generator to create a package.json for a project. Or install globally and run with Generate's CLI.
django-sql-dashboard - Django app for building dashboards using raw SQL queries
tsParticles - tsParticles - Easily create highly customizable JavaScript particles effects, confetti explosions and fireworks animations and use them as animated backgrounds for your website. Ready to use components available for React.js, Vue.js (2.x and 3.x), Angular, Svelte, jQuery, Preact, Inferno, Solid, Riot and Web Components.
govuk-form-builder - A form builder for Ruby on Rails that’s compatible with the GOV.UK Design System.
tsdx - Zero-config CLI for TypeScript package development
web.dev - The frontend, backend, and content source code for web.dev
pure-sh-bible - 📖 A collection of pure POSIX sh alternatives to external processes.
parcel - The zero configuration build tool for the web. 📦🚀
datasette - An open source multi-tool for exploring and publishing data
PIE - A behavior for Internet Explorer allowing it to recognize and render various CSS3 box decoration properties