deno-cliffy
pants
deno-cliffy | pants | |
---|---|---|
5 | 35 | |
863 | 3,105 | |
- | 1.1% | |
7.9 | 9.8 | |
27 days ago | 3 days ago | |
TypeScript | Python | |
MIT License | Apache License 2.0 |
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.
deno-cliffy
- The xz attack shell script
-
Bun 1.1
Also with Deno, it become very easy to write typed cli. .ts file can be run as script very easily with permission access defined on top of the script such as:
#!/usr/bin/env -S deno run --allow-net
Then one can just run ./test.ts if the script has +x permission.
Also project such as https://cliffy.io has made writing cli way more enjoyable than node.
It is a good idea to beware of the VC. So it is good idea to support project such as Hono (projects conform to modern web standard, and is runtime agnostic for JS).
-
Create a commit message in an interactive format.
import * as hoipoiCapsule from "https://deno.land/x/[email protected]/mod.ts"; const commitMessageTemplate = `{{type}}({{scope}}): {{summary}} {{body}} BREAKING CHANGE: {{breakingChange}}`; hoipoiCapsule.useCase.fillInCommitMessage.run({ commitMessageTemplate, questionList: [ { /** * The answer applies to the {{type}} part of commitMessageTemplate. */ target: "type", /** * Pre-prepared questions. */ q: hoipoiCapsule.preset.fillInCommitMessage.conventionalcommits.qMap.type, /** * Thus, you can also create your own questions. */ // q: typeQ, /** * Modify the commit message. * Use this function when a message is unanswered, for example. */ fixCommitMessage: (p) => { if (p.answerMap["type"] === "???") { return p.commitMessage.replace(/\r?\n{2,}/, "\n").trim(); } return p.commitMessage; }, }, ], }); /** * Please check here. * https://github.com/c4spar/deno-cliffy */ const typeQ = () => hoipoiCapsule.userInterface.prompt.Select.prompt({ message: "Select type.", search: true, options: [ { name: "Build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)", value: "Build", }, { name: "CI: Changes to our CI configuration files and scripts (examples: CircleCi, SauceLabs)", value: "CI", }, { name: "Docs: Documentation only changes", value: "Docs" }, { name: "Feat: A new feature", value: "Feat" }, { name: "Fix: A bug fix", value: "Fix:" }, { name: "Perf: A code change that improves performance", value: "Perf" }, { name: "Refactor: A code change that neither fixes a bug nor adds a feature", value: "Refactor", }, { name: "Test: Adding missing tests or correcting existing tests", value: "Test", }, ], });
-
githooked - The Deno git-hook handler for your lifecycle.
Just wanted to add that v0.0.6 has been released. I changed to a more refined CLI library using https://github.com/c4spar/deno-cliffy/ so that it can be more easily maintained. Still works just the same, but more refined and clean code since when it may have been previously looked at.
- C4spar/deno-cliffy: Command line framework for deno
pants
-
The xz attack shell script
> C/C++'s header system with conditional inclusion
Wouldn't it be more accurate to say something like "older build systems"? I don't think any of the things you listed are "modern". Which isn't a criticism of their legacy! They have been very useful for a long time, and that's to be applauded. But they have huge problems, which is a big part of why newer systems have been created.
FWIW, I have been using pants[0] (v2) for a little under a year. We chose it after also evaluating it and bazel (but not nix, for better or worse). I think it's really really great! Also painful in some ways (as is inevitably the case with any software). And of course it's nearly impossible to entirely stomp out "genrules" use cases. But it's much easier to get much closer to true hermeticity, and I'm a big fan of that.
0: https://www.pantsbuild.org/
-
Monorepo + Microservices + Dependency Managment + Build system HELL
Does pants/bazel can help me?
- Pants 2: The ergonomic build system
-
Go Dependency management in large company projects - How do you do it?
Hyper-large tech companies managing hyper-large monorepos using Bazel (google), buck (Facebook), please (thought machine), pants (Twitter, Foursquare & Square) enjoy them but also have a lot of resources devoted to running and maintaining it.
-
Reason to use other Build Tool than Make?
Yeah there's definitely some alternatives out there. Pants is another one that has a lot of traction.
-
Is it possible pickle a function with its dependencies?
You should look into pex, or itβs parent build system pants. A PEX (Python EXecutable) file can package up all your code including dependencies and run on another machine of similar OS with just an available compatible interpreter.
-
Sanity check of my decision for "Iterative AI" (DVC, MLEM, CML) pipeline over Azure ML
We don't have the CD yet, but I think what I put in place counts as simple CI (even if incomplete)? Every push & PR trigger an azure pipeline, which runs pants. This install the dependencies from the lockfile, run some linters, uses DVC to pull the data necessary for tests, and run unit tests (mypy check is deactivated until I solve a weird error). Basically the same script runs on laptops cross-platform (one of us uses Max, one Ubuntu with GPU, one Ubuntu with CPU, the scripts runs on every platform). The only difference with CI is the installation of Pants and the gestion of Cache (needs to be downloaded in CI so it takes ~3min in CI versus 20 seconds on my laptop).
- Pants 2: fast, scalable, user-friendly build system for codebases of all sizes
-
Maintain a Clean Architecture in Python with Dependency Rules
This has also been recently integrated in pants.
https://github.com/pantsbuild/pants/issues/13393
- Blazing fast CI with MicroVMs
What are some alternatives?
node-cli-boilerplate - πͺ Create node cli with this user friendly boilerplate
Bazel - a fast, scalable, multi-language and extensible build system
yaclt - Yet Another Change Log Tool
megalinter - π¦ MegaLinter analyzes 50 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally.
denoliver - A simple, dependency free static file server for Deno with possibly the worst name ever.
please - High-performance extensible build system for reproducible multi-language builds.
forge-node-app - π π¦π Generate Node.js boilerplate with optional libraries & tools
pyflow - An installation and dependency system for Python
deno-eclipt - A flexible Deno library to create CLIs
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
auto - Auto is a TypeScript-powered command-line automation tool.
Buck - A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.