Yarn Link doesn't support path to match npm · yarnpkg/yarn#1100

(2 留言) (5 反應) (0 負責人)JavaScript (41,514 star) (2,731 fork)batch import

cat-featurehelp wantedneeds-discussiontriaged

描述

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

Bug

What is the current behavior?

kstone@kstone-mbp $PWD> yarn link .
yarn link v0.15.1
error Couldn't find a package.json (or bower.json) file in $HOME/.yarn-cache/.link
[...]

kstone@kstone-mbp $PWD> yarn link 
yarn link v0.15.1
success Registered "$PKG".
info You can now run `yarn link "$PKG"` in the projects where you want to use this module and it will be used instead.
✨  Done in 0.06s.

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

See above.

What is the expected behavior?

kstone@kstone-mbp $PWD> npm link .
[...]
/usr/local/lib/node_modules/$PKG -> $PWD

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

kstone@kstone-mbp $PWD> node --version
v6.8.1
kstone@kstone-mbp $PWD> yarn --version
0.15.1
kstone@kstone-mbp $PWD> sw_vers 
ProductName:    Mac OS X
ProductVersion: 10.12
BuildVersion:   16A319

貢獻者指南

技術棧: nodejsjavascript
領域: clideveloper experiencetooling
議題類型: bug
難度: 3
預計時間: 1-2 days
活動狀態: stale
清晰度: clear
前置要求: Basic understanding of Yarn CLIFamiliarity with symlinks and package linking
新手友善度: 60
研究方向: The issue requests adding path support to `yarn link`, mirroring `npm link .` behavior. The current implementation only links the current package by name. To fix, examine the `link` command in `src/cli/commands/link.js`. The expected behavior is that `yarn link .` should symlink the local package directory to the global node modules. Look for how npm implements this; likely using `fs.symlink`. The discussion in the issue and linked PRs may provide hints.