vuetorrent: init at 2.18.0

[redxtech]

VueTorrent

The sleekest looking WEBUI for qBittorrent made with Vuejs!

VueTorrent is an alternative frontend/webui for qbittorrent.

Homepage/Repo: https://github.com/VueTorrent/VueTorrent
Live Demo: https://vuetorrent.github.io/demo
License: GPL-3.0
Package Request: #296190

Usage:
Within qbittorrent, point the custom webui directory to "${pkgs.vuetorrent}/var/www/vuetorrent".

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[redxtech]

Comments have been implemented, only one question:

Since the initial PR was download a zip file and packaging the contents, I had the platforms set to platforms.all, but now that it's using buildNpmPackage, I'm not sure what platform to put.

Should I leave it as all? Or is there a subset that buildNpmPackage works with?

[steeleduncan]

@redxtech Thanks, I believe buildNpmPackage is fine with all platforms. Ofborg will let you know if there is an issue though!

[redxtech]

I'm not sure what's causing the build failure - it built when I ran it, but I didn't try any nixpkgs specific tests. Is there a better way to interpret the build failures? Because I'm not sure what the one in the ofborg-eval check is telling me.

trace: evaluation warning: The deprecated `type.functor.wrapped` attribute of the option `mergedLazyLazy` is accessed, use `type.nestedTypes.elemType` instead.

I haven't touched anything that would use any of those, at least any more than any other buildNpmPackage package would do.

Could this be somehow caused by lack of compatibility with some platform? Should I re-push with a more limited subset of the platforms?

[steeleduncan]

@redxtech I just tried it on linux and it was fine. I think maybe you are right and it is best to restrict to linux

[azuwis]

@ofborg eval

[azuwis]

I'm not sure what's causing the build failure

I think it was caused by something in master branch, I believe ofborg will eval against the merged code with this PR and current master.

Ofborg-evail succeed after another try.

I think maybe you are right and it is best to restrict to linux

Since qbittorrent and qbittorrent-nox are also available on darwin, I think we should also make vuetorrent available on darwin too.

[steeleduncan]

Since qbittorrent and qbittorrent-nox are also available on darwin, I think we should also make vuetorrent available on darwin too.

Agreed, was confused by the build errors, but as you say they seem to be gone now!

[ambroisie]

Small nit, can be merged without it.

[wolfgangwalther]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 358030

---

x86_64-linux

✅ 1 package built:

• vuetorrent

---

x86_64-darwin

✅ 1 package built:

• vuetorrent

---

aarch64-darwin

✅ 1 package built:

• vuetorrent