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
I think that we should drop Bower support (probably, after version 1.4.0 release of satellite.js) as it seems deprecated:
$ npm install -g bower
npm WARN deprecated bower@1.8.2: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
/home/ezze/.nvm/versions/node/v6.11.0/bin/bower -> /home/ezze/.nvm/versions/node/v6.11.0/lib/node_modules/bower/bin/bower
/home/ezze/.nvm/versions/node/v6.11.0/lib
└── bower@1.8.2
If anybody still uses Bower package of satellite.js consider switching to Yarn or NPM.
Another reason to drop Bower support is the following: anytime we change the source code of the library we should rebuild everything in dist directory including minified file which introduces a big diff even if a change was small. Dropping Bower we can exclude built files in dist from the repo.
The text was updated successfully, but these errors were encountered:
I think that we should drop Bower support (probably, after version 1.4.0 release of
satellite.js
) as it seems deprecated:The same depreaction warning is placed on Bower home page and Bower Github repo (there is also an issue).
If anybody still uses Bower package of
satellite.js
consider switching to Yarn or NPM.Another reason to drop Bower support is the following: anytime we change the source code of the library we should rebuild everything in
dist
directory including minified file which introduces a big diff even if a change was small. Dropping Bower we can exclude built files indist
from the repo.The text was updated successfully, but these errors were encountered: