Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop Bower support #40

Closed
ezze opened this issue Nov 22, 2017 · 2 comments
Closed

Drop Bower support #40

ezze opened this issue Nov 22, 2017 · 2 comments

Comments

@ezze
Copy link
Collaborator

ezze commented Nov 22, 2017

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

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 in dist from the repo.

@davidcalhoun
Copy link
Contributor

Sounds good, yeah it's deprecated from what I can tell.

@ezze
Copy link
Collaborator Author

ezze commented Dec 22, 2017

Dropped since 2.0.0.

@ezze ezze closed this as completed Dec 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants