-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Description
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
I have a bower.json in the root directory of a project alongside package.json.
The bower.json contents are:
{
"name": "my-project-name",
"version": "0.0.0",
"appPath": "src",
"resolutions": {
"angular": "^1.4.8"
},
"dependencies": {
"angular-material": "1.0.3-master-0918596",
"angular-ui-map": "~0.5.0",
"angular-tour-no-jQuery": "~0.2.6",
"ngclipboard": "^1.1.0"
}
}
Should Bower support work automatically?
(The package.json has a postinstall script that runs bower install. I've seen pre/post-install hooks don't currently get run as per #853, but yarn says it supports bower itself so...)
If the current behavior is a bug, please provide the steps to reproduce.
rm -rf node_modules bower_components
run yarn.
node_modules are populated but bower_components are not.
What is the expected behavior?
yarn reads the bower.json and populates the bower_components folder with bower dependencies.
yarn should also track the bower components in its yarn.lock file (related: #846)
Please mention your node.js, yarn and operating system version.
node 6.2.2
yarn 0.15.1 (installed globally with npm)
bower 1.7.9 (installed globally with npm)
OSX El Capitan