In reply to @purepani:matrix.org
how does that bug not make yarn-berry effectively useless to anyone

So, apparently this is at least somewhat intended, or at least intentionally not guaranteed: https://yarnpkg.com/cli/install.

First the package manager will resolve your dependencies. The exact way a dependency version is privileged over another isn't standardized outside of the regular semver guarantees. If a package doesn't resolve to what you would expect, check that all dependencies are correctly declared (also check our website for more information: ).
Specifically, they say
Note that running [yarn install] is not part of the recommended workflow. Yarn supports zero-installs, which means that as long as you store your cache and your .pnp.cjs file inside your repository, everything will work without requiring any install right after cloning your repository or switching branches.

The issue is that if the repos don't use zero-install, either by choice, or just because they don't realize that it's a thing, there's no way to get any type of reproducibility since the integrety hashes aren't stored.

In reply to @purepani:matrix.org
how does that bug not make yarn-berry effectively useless to anyone

So, apparently this is at least somewhat intended, or at least intentionally not guaranteed: https://yarnpkg.com/cli/install.

First the package manager will resolve your dependencies. The exact way a dependency version is privileged over another isn't standardized outside of the regular semver guarantees. If a package doesn't resolve to what you would expect, check that all dependencies are correctly declared (also check our website for more information: ).
Specifically, they say
Note that running [yarn install] is not part of the recommended workflow. Yarn supports zero-installs, which means that as long as you store your cache and your .pnp.cjs file inside your repository, everything will work without requiring any install right after cloning your repository or switching branches.

The issue is that if the repos don't use zero-install, either by choice, or just because they don't realize that it's a thing, there's no way to get any type of reproducibility since the integrety hashes aren't stored.

So, apparently this is at least somewhat intended, or at least intentionally not guaranteed: https://yarnpkg.com/cli/install.

First the package manager will resolve your dependencies. The exact way a dependency version is privileged over another isn't standardized outside of the regular semver guarantees. If a package doesn't resolve to what you would expect, check that all dependencies are correctly declared (also check our website for more information: ). Specifically, they say
Note that running [yarn install] is not part of the recommended workflow. Yarn supports zero-installs, which means that as long as you store your cache and your .pnp.cjs file inside your repository, everything will work without requiring any install right after cloning your repository or switching branches.

The issue is that if the repos don't use zero-install, either by choice, or just because they don't realize that it's a thing, there's no way to get any type of reproducibility since the integrety hashes aren't stored.

So, apparently this is at least somewhat intended, or at least intentionally not guaranteed: https://yarnpkg.com/cli/install.

First the package manager will resolve your dependencies. The exact way a dependency version is privileged over another isn't standardized outside of the regular semver guarantees. If a package doesn't resolve to what you would expect, check that all dependencies are correctly declared (also check our website for more information: ).

Specifically, they say

Note that running [yarn install] is not part of the recommended workflow. Yarn supports zero-installs, which means that as long as you store your cache and your .pnp.cjs file inside your repository, everything will work without requiring any install right after cloning your repository or switching branches.

The issue is that if the repos don't use zero-install, either by choice, or just because they don't realize that it's a thing, there's no way to get any type of reproducibility since the integrety hashes aren't stored.

Hello, just wondering what the process is for building my project locally from my Flake output.

I think the problem is how Flakes handle files in .gitignore? I have a dist/ folder that is generated via Webpack/Babel at build-time, and it is currently gitignore'd. Things work fine if I take it out of the .gitignore file and run git add dist/.

When I don't do that, the build fails with message: error: getting status of '/nix/store/miap1bv0r73waw5g52ln2gnqjq8848yl-source/dist': No such file or directory

I try to build the package using npmBuildPackage, which runs the npm run build script by default in the buildPhase. This is fine and it should use webpack/babel to produce a dist/ directory.

I don't define any custom buildPhase, but I do define a custom installPhase which is simply:

installPhase = ''
  runHook preInstall

  cp -r ./dist $out/dist

  runHook postInstall
'';

Any ideas on how to get this to work?