Skip to content

Instantly share code, notes, and snippets.

@sheerun
Last active March 19, 2023 02:27
Show Gist options
  • Star 22 You must be signed in to star a gist
  • Fork 8 You must be signed in to fork a gist
  • Save sheerun/c04d856a7a368bad2896ff0c4958cb00 to your computer and use it in GitHub Desktop.
Save sheerun/c04d856a7a368bad2896ff0c4958cb00 to your computer and use it in GitHub Desktop.
Proper .bowerrc file pointing to new Bower registry (if using legacy Bower version)
{
"registry": "https://registry.bower.io"
}
@sheerun
Copy link
Author

sheerun commented Jun 28, 2018

You can use bower-away to switch to yarn and preserve the rest of your setup

@ParsaGachkar
Copy link

my .bowerrc looks like this
{
"directory": "wwwroot/lib",
"registry": "https://registry.bower.io"
}
still can't install or update anything "Using Visual Studio 2018 in a dotnet core 2.0 web application project "

Gonna give a try with VSCode and CLI

@abepetrillo
Copy link

The newest version of bower really should point to the new registry by default, not the old one. Without this thread I would have been lost. Thanks @sheerun

@DanielRuf
Copy link

Should have been also in the deprecation notices probably ;-)

@bukandu1
Copy link

my .bowerrc looks like this
{
"directory": "wwwroot/lib",
"registry": "https://registry.bower.io"
}
still can't install or update anything "Using Visual Studio 2018 in a dotnet core 2.0 web application project "
Gonna give a try with VSCode and CLI

Did you get it to work after using VSCode and CLI? My .bowerrc looks like this as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment