NodeJS packages do not follow the Flake output schema about dream2nix HOT 3 CLOSED

I did it now a bit different. Alternative 2 has the problem that the other version attributes will be mixed with all other stuff which the derivation passes through. This would be bad for automation. Therefore I went for:
Alternative 3:

packages.{system} = {
  foo = {latest-foo-package};
  foo.versions."1.0.0" = ...;
  foo.versions."1.2.0" = ...;
}

from dream2nix.

Thanks for looking into this. The design is not finalized yet. I totally agree this must be changed. I currently have 2 alternative schemas in mind. Let me know about your opinion.

Alternative 1 (package name and version in attribute name):

packages.{system} = {
  foo-latest = {latest-foo-package};
  "foo-1.0.0" = ...;
  "foo-1.2.0" = ...;
}

Alternative 2 (one attribute for latest package; other versions inside passthru of latest):

packages.{system} = {
  foo = {latest-foo-package};
  foo."1.0.0" = ...;
  foo."1.2.0" = ...;
}

Alternative 1 makes all attributes clearly visible on the top level.
Alternative 2 is better for automation tools which want to simply list all available versions for a specific package.
Maybe we should do a mix of 1 & 2.

from dream2nix.

I prefer the second alternative because it is more obvious which is the canonical version of the package. Also, it avoids exporting the same derivation under two different attributes (foo-latest and foo-1.2.0 in this example).

The first schema would be more suitable for the checks output, if you choose to provide that, as it means each individual version is tested by nix flake check.

from dream2nix.