build: update nix flake

[uael]

• update lock file
• improve npm client package using pkgs.buildNpmPackage
• improve windmill package

---

Important

Update Nix flake to enhance npm and Rust package builds, including lock file updates and new build inputs.

• Lock File Update:
  • Update flake.lock with new revisions and hashes for nixpkgs and rust-overlay.
• NPM Client Package:
  • Use pkgs.buildNpmPackage for windmill-client in flake.nix.
  • Add npmDepsHash and npmBuild for build process.
  • Modify postUnpack and preBuild phases.
• Windmill Package:
  • Update buildFeatures in flake.nix to include new features like enterprise, stripe, prometheus, etc.
  • Add RUSTY_V8_ARCHIVE and FRONTEND_BUILD_DIR environment variables.
• Build Inputs:
  • Add libtool to buildInputs in flake.nix.
  • Include self.packages.${system}.windmill-client and pkgs.perl in nativeBuildInputs for windmill.

^{This description was created by for 628fc9b. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 628fc9b in 39 seconds

More details

• Looked at 176 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. flake.nix:40

• Draft comment:
  Using pkgs.lib.fakeHash for x86_64-darwin is not recommended. Consider using a valid hash or add a comment explaining the use of a fake hash.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  Using fakeHash is generally a temporary solution that needs to be replaced with a real hash. However, this could be intentional - perhaps the x86_64-darwin build isn't supported yet or the hash will be filled in later. The comment doesn't provide strong evidence that this is definitely wrong, just that it's not recommended.
  I might be too quick to dismiss this - using fakeHash could cause build failures on x86_64-darwin systems. The comment could help prevent issues.
  While build failures are possible, the author likely knows this is a placeholder. The comment doesn't provide actionable guidance on what the correct hash should be, and the use of fakeHash may be intentional during development.
  The comment should be deleted as it's more of a suggestion than a clear issue requiring change, and the use of fakeHash may be intentional.

2. flake.nix:114

• Draft comment:
  doCheck is set to false, which disables tests. Ensure this is intentional to avoid missing potential issues. This applies to other instances as well.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The doCheck attribute is set to false in multiple places. This might be intentional, but it's worth noting that it disables tests, which could lead to undetected issues.

3. flake.nix:140

• Draft comment:
  Ensure buildInputs and nativeBuildInputs are correctly categorized to avoid build issues. Check for any overlap or misplacement of dependencies.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The buildInputs and nativeBuildInputs are defined separately, but there might be overlap. It's important to ensure that dependencies are correctly categorized to avoid build issues.

Workflow ID: wflow_2g39ycYtUpawHcmB

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[cloudflare-workers-and-pages]

Deploying windmill with    Cloudflare Pages

Latest commit:	628fc9b
Status:	✅  Deploy successful!
Preview URL:	https://0a3be788.windmill.pages.dev
Branch Preview URL:	https://uael-update-nix.windmill.pages.dev

View logs