Bower: Bower deprecation warning points to non-existent blog post

[IGx89]

I'm seeing the following message when using Bower: "psst! While Bower is maintained, we recommend yarn and webpack for new front-end projects! Please read our blog for more."

However, I can't find the blog post referred to. I Google'd and https://bower.io/blog/ appears to be the official blog, but nothing on there talks about Bower being deprecated. I see posts about "Bower is growing!" and "What's new in bower", as well as a post recommending trying Yarn (but then saying Yarn has temporarily dropped support for bower).

Am I missing something? Was the blog post deleted? I was expecting to see a post about why Bower is deprecated now (graphs of declining usage, areas its lacking in, developers moving on, etc.) and helpful instructions on how to upgrade Bower apps to Yarn/Webpack.

[sheerun]

It's the one about Yarn and its advantages compared to Bower.

On Tue, 23 May 2017 at 20:11, Matthew Lieder [e-mail]
wrote:

I'm seeing the following message when using Bower: "psst! While Bower is
maintained, we recommend yarn and webpack for new front-end projects!
Please read our blog for more."

However, I can't find the blog post referred to. I Google'd and
https://bower.io/blog/ appears to be the official blog, but nothing on
there talks about Bower being deprecated. I see posts about "Bower is
growing!" and "What's new in bower", as well as a post recommending trying
Yarn (but then saying Yarn has temporarily dropped support for bower).

Am I missing something? Was the blog post deleted?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bower/bower/issues/2460, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAR2DYuvUrjPDcO_NVoeyB3POcTX39bsks5r8yExgaJpZM4NkEuW
.

[dequis]

It's the one about Yarn and its advantages compared to Bower.

But that post says

UPDATE: Yarn decided to drop Bower support for now. We recommend to try it anyway as an alternative to npm!

Which sounds like yarn isn't really a replacement

[panuhorsmalahti]

And now that npm v5 is released, there's little benefit from yarn over npm. I'd probably change yarn to npm now, even if npm v5 doesn't have special bower support.

[sheerun]

Yarn supports full flatttning and right now is reported to be more stable
and little faster. I'd consiter it in few months, not right after the
release.
On Wed, 31 May 2017 at 11:28, Panu Horsmalahti [e-mail]
wrote:

And now that npm v5 is released, there's little benefit from yarn over
npm. I'd probably change yarn to npm now, even if npm v5 doesn't have
special bower support.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/bower/bower/issues/2460#issuecomment-305136760, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAR2DeIAJbjRkt8EP5exe8TIsdtAsQaeks5r_TLQgaJpZM4NkEuW
.

[neilsh]

Would it be possible to include some info on how one would actually transition to yarn/webpack? As it currently stands the message is pretty confusing.

[sheerun]

Currently there's no transition path, that's why it says "for new projects".

We could publish an article how to migrate from bower to yarn, but currently it's blocked by non-ability of yarn installing git repositories without package.json: https://github.com/yarnpkg/yarn/pull/2651

As soon as yarn is released with this feature we could write the article or tool to migrate.

[sheerun]

I've changed deprecation message on npm install -g bower to hopefully something better:

..psst! While Bower is maintained, we recommend Yarn and Webpack for new front-end projects! Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's no migration path but we hope you'll help us figure out one.