Can I replace bower with yarn ?

[warpdesign]

The announcement post says that yarn can be used with bower workflows: can it replace bower as well?

How? The documentation doesn't seem to mention bower migration.

[sebmck]

Hey! Thanks for the question. We're still in the process of ironing out how the integration between npm and bower actually works. Suffice to say, you should be able to run yarn install from inside of a directory with bower.json and have it install all dependencies and work as you'd expect!

[panuhorsmalahti]

As far as I understand, you need to use yarn in flat mode with yarn install --flat.

[warpdesign]

@kittens doesn't seem to work.

I have both bower.js & package.json in the same directory. Running yarn from this directory installs npm packages but not bower ones.

[dsschnau]

@panuhorsmalahti yarn install --flat didn't seem to do anything with bower deps. (though it did install node_modules flatly.

[mattbucci]

Doesn't seem to be any documentation around this either at this time, although it is mentioned in the blog post.

[NamPNQ]

@warpdesign Workarround, just rename the package.json and run yarn 💃

[panuhorsmalahti]

@dsschnau, sorry, I kinda misunderstood this issue, I thought it was about how to replace bower by using the npm registry - which is what the --flat flag can be used for.

[slbug]

Will be useful to have ability to install packages from package.json and bower.json at the same time.

[jonathanong]

i would like a feature/option to only install bower.json so that i can ditch bower. replacing npm with yarn would be a separate step for me, but that's lower priority for me as npm isn't as broken as bower :P

[omnisite]

If you add the following to package.json, bower install will be called and it works. It is a workaround though:

"scripts": { "postinstall": "bower install" }

[bennypowers]

@dsschnau This affects Polymer workflows with yarn when certain dependencies are required.
e.g.

bower.json

dependencies: {
  "app-localize-behavior": "PolymerElements/app-localize-behavior#^0.9.2"
}

yarn install --flat fails to install intl-messageformat, which app-localize-behavior depends on

[tony19]

@bennyp123 intl-messageformat is actually installed under node_modules instead of bower_components (due to #715). See workaround.

[wyze]

Bower support has been dropped in #1441.

[warpdesign]

@wyze is it planned for later or definitely dropped ?

The idea of using Yarn for both npm & bower sounded a good idea to me.

[wyze]

I am not sure what the future plans are. I think there will be a roadmap released eventually that will give more clarity.

[alextreppass]

Support for bower was removed, see #1441.

[graingert]

@warpdesign

Bower is on it's way out and we shouldn't be supporting it.

and

bring over the features they like from Bower to Yarn (such as flat install which we already have and other unimplemented features like svn support etc).

However it looks the bower package registry is not going to be used.

[warpdesign]

@graingert Ok. Fair enough.

[hickscorp]

As @omnisite mentioned, "scripts": { "postinstall": "bower install" } in your npm task does the trick. We use bower-locker to have proper semantic dependency locking, and it's all shiny!

[mvasilkov]

Rest in pepperoni, sweet feature.

Such sad.

[qknight]

can someone point out alternatives then? or should one still stick to bower at the time being?

[graingert]

`yarn install --flat` or yarn with webpack

…

On 28 Jun 2017 12:05 pm, "Joachim Schiele" ***@***.***> wrote: can someone point out alternatives then? or should one still stick to bower at the time being? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#617 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAZQTA9XuzEoaxikJ-0usVZ-0pzKF_f6ks5sIjNqgaJpZM4KTzmP> .

[mokiding]

https://medium.com/@andrejsabrickis/bye-bye-bower-or-how-to-migrate-from-bower-to-npm-and-webpack-4eb2e1121a50

Meybe this post can help you about migrating from bower ...

[nbonamy]

I am sticking to yarn as a bower replacement for the moment and solved all this by:

1. Removing @bower_components prefix on all components
2. Properly split devDependencies and dependencies (so front-end ones)
3. Set the postinstall script to "node install.js"
4. Install.js being https://gist.github.com/nbonamy/7019b7a42e7e53dee2a587590a164c39. The root const needs to be adjusted to your setup.

If that can help anyone...