sanitizeDerivationName seems unnecessary

[wmertens]

there's

{
  sanitizeDerivationName = name:
    lib.replaceStrings ["@" "/"] ["__at__" "__slash__"] name;
}

which results in long and unreadable names for modules like __at__babel__slash__runtime, and there's no technical need for it, since Nix will sanitize names like @babel/runtime to -babel-runtime.

How about not sanitizing derivation names?

[tinybeachthor]

I think this makes sense.
I prefer the shorter name, and there is no real information lost between __at__babel__slash__runtime and -babel-runtime.

Could this change break anything though?

[wmertens]

No breaking change, it only means rebuilding packages

[DavHau]

I'm not opposed to removing the custom sanitizing. I just thought, that with -babel-runtime it might not be clear on first glance if this is a namespaced package or a package called babel-runtime, but actually the - indicates a namespace.
But if we had @babel/runtime-foo it would be rendered to -babel-runtime-foo, making it unclear if runtime is part of the namespace or package name.

[wmertens]

In any case, RFC #17 proposes doing away with names in store paths, and the actual name of the package is evident in the lib/node_modules directory.

So I don't think there's much opportunity for confusion.

[DavHau]

OK, I'm fine with removing the use of sanitizDerivationName.

[tinybeachthor]

Resolved in #315