continua a ser o gerenciador de pacotes de escolha para muitos times. Recebemos com entusiasmo o lan?amento do Yarn 2, um novo release importante, com uma longa lista de mudan?as e melhorias. Al¨¦m de ajustes de usabilidade e melhorias na ¨¢rea de espa?os de trabalho, o Yarn 2 introduz o conceito de zero-installs, que permite ¨¤s pessoas desenvolvedoras executar um projeto diretamente ap¨®s clon¨¢-lo. No entanto, o Yarn 2 inclui algumas mudan?as importantes que tornam a atualiza??o . Ele tamb¨¦m traz ambientes (PnP) como padr?o, mas n?o oferece suporte ao React Native em ambientes PnP. Os times podem, ¨¦ claro, desabilitar o PnP ou permanecer no Yarn 1. No entanto, eles devem estar cientes de que o Yarn 1 est¨¢ agora em modo de manuten??o.
is a fast, reliable and secured package manager for JavaScript. Using a lock file and a deterministic algorithm, Yarn is able to guarantee that an installation that worked on one system will work exactly the same way on any other system. By efficiently queuing up requests, Yarn maximizes network utilization and as a result we¡¯ve seen faster package downloads. Yarn continues to be our tool of choice for JavaScript package management in spite of the latest improvements in npm (version 5).
is a new package manager that replaces the existing workflow for the npm client while remaining compatible with the npm registry. With the npm client, we may end up with a different tree structure under node_modules based on the order that dependencies are installed. This nondeterministic nature can cause "works on my machine" problems. By breaking the installation steps into resolution, fetching and linking, Yarn avoids these issues using deterministic algorithms and lockfiles and thus guarantees repeatable installations. We've also seen significantly faster builds in our continuous integration (CI) environment because of Yarn caching all the packages it downloads.
is a new package manager that replaces the existing workflow for the npm client while remaining compatible with the npm registry. With the npm client, we may end up with a different tree structure under node_modules based on the order that dependencies are installed. This nondeterministic nature can cause "works on my machine" problems. By breaking the installation steps into resolution, fetching and linking, Yarn avoids these issues using deterministic algorithms and lockfiles and thus guarantees repeatable installations. We've also seen significantly faster builds in our continuous integration (CI) environment because of Yarn caching all the packages it downloads.
