conventional-changelog/commitlint

CommitLint with Yarn v2 (Plug'n'play)

Open

#2,637 创建于 2021年6月7日

在 GitHub 查看
 (17 评论) (3 反应) (0 负责人)TypeScript (15,497 star) (896 fork)batch import
featurehelp wanted

描述

Expected Behavior

In the yarn v1 and yarn v2 (with nodeLinker: node_modules), commitlint work perfectly

Current Behavior

It doesn't work at all. I've tried these command in git-hook (husky):

  • npx --no-install commitlint --edit "$1"
  • yarn --no-install commitlint --edit "$1"
  • yarn run --no-install commitlint --edit "$1"

Here is the pictures of this problem: Screen Shot 2021-06-07 at 12 33 55

Screen Shot 2021-06-07 at 12 34 31

Screen Shot 2021-06-07 at 12 34 51

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Steps to Reproduce (for bugs)

Link for my repo (bypass git hook)

  1. yarn init && yarn set version berry
  2. yarn add -D @commitlint/config-conventional @commitlint/cli husky
  3. yarn husky install
  4. echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js
  5. npx husky add .husky/commit-msg 'npx --no-install commitlint --edit "$1"'
  6. Commit change

Context

Your Environment

Mac OS X 10.11.6 El Captain

Executable Version
commitlint --version bash: commitlint: command not found
yarn run commitlint --version @commitlint/cli@12.1.4 (Need yarn run, see here
git --version git version 2.29.2
node --version v14.15.3

贡献者指南

技术栈
typescriptnodejsshell
领域
clitooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic knowledge of Yarn v2Understanding of commitlint configurationFamiliarity with git hooks
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
The issue is about commitlint not working with Yarn v2's Plug'n'play mode. The user reports that commands like 'npx no install commitlint' fail. Investigate how commitlint resolves its dependencies when using Yarn v2 PnP. Check the commitlint CLI entry point and whether it properly loads packages using Node.js's resolver. Look into the Yarn v2 documentation on PnP and how to make packages compatible. Consider adding a Yarn specific resolution or using 'yarn node' to execute. Also review any existing comments in the issue for attempted solutions. Key files to examine: packages/cli/src/cli.js or similar and the package.json for dependencies.