yarnpkg/yarn

Yarn audit does not work with an external repository

Open

#7,012 创建于 2019年2月7日

在 GitHub 查看
 (11 评论) (14 反应) (0 负责人)JavaScript (41,514 star) (2,731 fork)batch import
good first issuehelp wanted

描述

Do you want to request a feature or report a bug? Bug

What is the current behavior?

When running yarn audit with the --registry flag, it uses the main yarn repo anyway.

If the current behavior is a bug, please provide the steps to reproduce.

Execute yarn audit --registry https://registry.npmjs.org/

What is the expected behavior?

Audit calls are made to the defined registry. This is especially important for everyone with third party repo's where the outside world it blocked on CI agents. Or if you're using some kind of proxy.

Please mention your node.js, yarn and operating system version.

Mac Os Mojave Yarn 1.13.0 Node 10.15.1

贡献者指南

技术栈
javascriptnodejs
领域
cli
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Familiarity with Yarn CLIBasic Node.jsUnderstanding of package registries
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate how the ` registry` flag is handled in the audit command. Look at the source code in `src/cli/commands/audit.js` to see where the registry URL is used. Check if there is a fallback to the default registry. Review existing tests for audit with custom registries and consider adding a test that verifies the API call URL when ` registry` is passed.