Yarn's Future - v2 and beyond · Issue #6953 · yarnpkg/yarn
Hi everyone, When the Yarn project started back in 2016, our landscape was very different from what it is now. Package locking was far from being a first class citizen in the Javascript ecosystem, and the time needed to run an install was ... well, it was what it was. Yarn's release shook the status quo and started a movement that ended up being beneficial to everyone, other package managers inclu
Yarn Plug'n'Play: Getting rid of node_modules by arcanis · Pull Request #101 · yarnpkg/rfcs · GitHub
This PR is locked to prevent sending notifications to people who are only interested in the high-level design. For any technical issue, please direct your questions to the Yarn repository. Note: This PR's discussions should be focused on the high-level design. A separate PR has been opened on the code repository to discuss the implementation details. A pdf has been generated and made available her
403 error page from CloudFlare on https://registry.yarnpkg.com · Issue #5885 · yarnpkg/yarn
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Pick a username Email Address Password Sign up for GitHub By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account
feat(import): convert package-lock.json to yarn.lock by imsnif · Pull Request #5745 · yarnpkg/yarn
This is the first step to addressing: #5654 Overview (TLDR) At the moment, one is able to yarn import using node_modules as the dependency-tree state to create a yarn.lock file. The feature created by this PR allows one to yarn import using package-lock.json as the dependency-tree state. When one enters the yarn import command, if a package-lock.json file exists, yarn would attempt to import from
Competing lockfiles create poor UX · Issue #5654 · yarnpkg/yarn
NB: I'm creating this issue in the yarn repo, but this is actually a shared issue between yarn and npm. With the release of npm 5 back in May, the Node ecosystem now has two lockfile-based package managers. This was overall a win for users, and it has been good to see competition in this space. However now that there are two competing lockfile formats this can create a new problem for users, espec
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
[Feature] Add support for `yarn npm publish --provenance` and `publishConfig.provenance` option · Issue #5430 · yarnpkg/berry
GitHub - yarnpkg/berry: 📦🐈 Active development trunk for Yarn ⚒
feat(auth): Support two factor authentication for NPM accounts by neonowy · Pull Request #6555 · yarnpkg/yarn
support gitHead property in package.json · Issue #2978 · yarnpkg/yarn
Can't publish package with NPM account that has enabled 2FA · Issue #4904 · yarnpkg/yarn
🦁 Yarn 2.0 Working Group · Issue #5773 · yarnpkg/yarn
What is the role of 'registry.yarnpkg.com'? · Issue #889 · yarnpkg/yarn
Update: add DNS caching to request manager by BYK · Pull Request #4447 · yarnpkg/yarn
Fix: Use semver tag to colorize package name for outdated/upgrade-interactive commands by CarlRosell · Pull Request #4183 · yarnpkg/yarn
upgrade-interactive row colours are incorrect · Issue #3815 · yarnpkg/yarn
CLI - yarn upgrade's behavior is not as expected · Issue #3492 · yarnpkg/yarn
Fixies for running with artifactory 4.14.1 by rogeriochaves · Pull Request #3172 · yarnpkg/yarn
Add RFC for install scripts whitelist by voxpelli · Pull Request #76 · yarnpkg/rfcs
Idea: support package-lock.json from npm 5 · Issue #3614 · yarnpkg/yarn
An unexpected error occurred: Request failed \"404 Not Found\"". · Issue #2738 · yarnpkg/yarn
