playwright-driver: fix eval on Nix 2.3

[philiptaron]

Motivation for changes

Fix evaluation on nixVersions.minimum (Nix 2.3) so that nixpkgs-vet is able to work on all versions of Nix that are supported in nixpkgs.

This was detected with nixpkgs-vet's automated update: NixOS/nixpkgs-vet#114

Description of changes

Nix 2.3 doesn't support the ./${name}.nix syntax that #298944 uses. Instead, it uses the clunkier ./. + "/${name}.nix" syntax.

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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

[Mic92]

In this case we can probably make an exception, but eventually I don't think we should hold back using newer features if they benefit in nixpkgs.

[philiptaron]

In this case we can probably make an exception, but eventually I don't think we should hold back using newer features if they benefit in nixpkgs.

It's shocking how few new features are accidentally used -- the backwards compatibility is quite good, massive kudos to the Nix and Lix teams for this. The last PR of this sort was #329212 in July, and just like this one, was trivial to spot and remediate.

The day will obviously come when nixVersions.minimum is raised to some newer version of Nix. Before that, let's keep the compatibility, especially if it doesn't have a big maintenance burden -- which, based on the evidence and the Nixpkgs-wide test that nixpkgs-vet uses, is quite low!

[phaer]

Thanks for catching & fixing :)