Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

accept BOWER_FLAGS like NPM_FLAGS and YARN_FLAGS #108

Closed
fool opened this issue Nov 30, 2017 · 3 comments
Closed

accept BOWER_FLAGS like NPM_FLAGS and YARN_FLAGS #108

fool opened this issue Nov 30, 2017 · 3 comments
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@fool
Copy link
Contributor

fool commented Nov 30, 2017

since there is no way to NOT run bower install if there is a /bower.json - we should allow users to pass flags like we do for NPM and YARN

@c0b41
Copy link

c0b41 commented Dec 27, 2017

Bower deprecation soon also yarn support bower installing https://bower.io/blog/2017/how-to-migrate-away-from-bower/

@brycekahle
Copy link
Contributor

Bower is actively encouraging folks to migrate to yarn. I do not think we should add new features for it.

@oskarrough
Copy link

For anyone ending up here from a search. Older versions of bower use a registry that might fail on Netlify with a "EINVRES failed 502" error.

If you can't upgrade bower, tell bower to use the new registry with a .bowerrc file. Like this:

{
  "registry": "https://registry.bower.io"
}

@verythorough verythorough added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Feb 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

No branches or pull requests

5 participants