ultra-runner
nixpkgs
Our great sponsors
ultra-runner | nixpkgs | |
---|---|---|
4 | 973 | |
1,187 | 15,656 | |
- | 5.3% | |
0.0 | 10.0 | |
5 days ago | about 13 hours ago | |
TypeScript | Nix | |
Apache License 2.0 | 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.
ultra-runner
-
Directly point to source code when referencing dependencies in monorepo
Cache built files to avoid rebuilds. For example nx.js, yarn-plugin-change, ultra-runner
-
Next.js monorepo build process optimization
Then comes the question of triggering docker builds if you need to release images. If you have many apps, it's better to create a docker file for each, so you can decide which one needs to be built. Nx help in this area, because it can compute which apps needs to be rebuilt... If you have only few apps you can use github action paths (ie: simplified example) or eventually make use of things like [ultra-runner](https://github.com/folke/ultra-runner). Anyway docker and nextjs take times to setup (env...). It's another story.
-
What is monorepo? (and should you use it)
ultra-runner: scripts for JavaScripts monorepo management. Plugs in with Yarn, pnpm, and Lerna. Supports parallel building.
-
JavaScript Monorepo Tooling
🏃 ultra-runner
nixpkgs
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
-
GitHub Disabled the Xz Repo
True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)
It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.
That is the problem.
-
Combining Nix with Terraform for better DevOps
We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.
What are some alternatives?
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
nextjs-monorepo-example - Collection of monorepo tips & tricks
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
yarn.build - Build 🛠 and Bundle 📦 your local workspaces. Like Bazel, Buck, Pants and Please but for Yarn Berry. Build any language, mix javascript, typescript, golang and more in one polyglot repo. Ship your bundles to AWS Lambda, Docker, or any nodejs runtime.
git-lfs - Git extension for versioning large files
pnpm - Fast, disk space efficient package manager
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
npm-lint - A linter for npm & node package.json files with a focus on dependency security
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.