You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compared to "npm", yarn currently does not add symlinks for binaries in deep dependencies to the ".bin" folder. I heavily rely on this for the advanced boilerplate which is basically a dependency for all my react project. I try to keep dependencies central in this one repository instead of listing everything in my application projects.
BTW: Yarn also complains a lot on these non direct dependencies. This also differs from npm which, based on the "new" flat "node_modules" folder, just works. With the exceptions of the binary symlinks yarn works here as well - the question is only if these warnings are really needed when the dependencies are fully fulfilled after the installation.
Compared to "npm", yarn currently does not add symlinks for binaries in deep dependencies to the ".bin" folder. I heavily rely on this for the advanced boilerplate which is basically a dependency for all my react project. I try to keep dependencies central in this one repository instead of listing everything in my application projects.
BTW: Yarn also complains a lot on these non direct dependencies. This also differs from npm which, based on the "new" flat "node_modules" folder, just works. With the exceptions of the binary symlinks yarn works here as well - the question is only if these warnings are really needed when the dependencies are fully fulfilled after the installation.
Example:
React 15, eslint and stylelint are all installed through the "advanced boilerplate" which is listed in the "dependencies" in "package.json".
The text was updated successfully, but these errors were encountered: