Is it possible to change the name of a bower package after you register it?
I have created a package and pushed up, but I have made a typo.
Can I change this information in a later version?
Unfortunately there is currently no way for package publishers to interact with the Bower registry, that includes unregister / rename. You can make a request for a manual edit here:
https://github.com/bower/bower/issues/120
However this will be available in the future once registry rewrite is done:
https://github.com/bower/registry/issues/73
Related
We've published a package with two artifacts in it (android and os) to Bintray: https://dl.bintray.com/gojuno/maven/com/gojuno/commander/
Then we've enabled sync with jcenter for this package, but only one of the artifacts is in sync (android is synched while os is not):
https://jcenter.bintray.com/com/gojuno/commander/
I contacted Bintray through Inbox on bintray.com, Contact Us on bintray.com, Email and Twitter and haven't received reply anywhere, this issue is blocking for the project.
I saw similar issue was resolved through StackOverflow Bintray and JCenter not in Sync, so this is my hope.
An inclusion to JCenter always uses an allocated path prefix to avoid accidental file overwrites by other users. However, the 'commander' package contains files with no common base path:
'/com/gojuno/commander/os' AND '/com/gojuno/commander/android'
The best practice we recommend is creating a new package and not creating more than one path prefix for a package. If you wish keep working like this, please note that you will have to submit an inclusion request for each path prefix.
As for now you may proceed working on the same groupID path prefix with your different sub-modules.
We hope this clarifies.
usually when changing the artifact path you won't be able to resolve your content through JCenter although it was previously included.
The reason for this is that the inclusion of your 'commander' package in JCenter is for the files’ path.
Therefore, it was originally included under the path prefix 'com/gojuno/commander/android/'.
However, we have re-linked your package on the GroupId level (com/gojuno/commander) so every sub-module of your 'commander' package, will be added automatically and be synced with JCenter.
I see that there are new versions of ASP.NET MVC and Web API
If a solution references these NuGet packages, will it automatically update them to these newer versions with options set thus:
?
No, you still need to go to the package manager, and check the updates section.
The setting here allow the project, when built for the first time, to go to nuget and fetch the dependant assemblies. For example, if a colleague was to get the solution for the repo for the first time, when they build, all the assemblies will be downloaded.
NOTE: Be careful when updating, I usually tend to do it in small bunches at a time and check the solution still runs / builds after each update.
No. NuGet does not automatically upgrade packages. If you want to update a package, you'll need to do it manually.
However, NuGet will download missing referenced packages in order to allow a project to build correctly, which is what those options reference. There's more information on Package Restore over at NuGet.org.
Is there a way to inclusively specify which files I want served when a user does a
bower install MY_PACKAGE
Right now, there is a ignore array where I can add the files which I want excluded. There is a proposal to do something like this, but I want to know if someone out there has already hacked his way into doing it.
Use the source control facility of your choice, such as:
Git tag
Git branch
Subversion revision
to distribute an artifact ID rather than the package name.
We're using bower to manage all of our front-end dependencies for our project. I've run into an issue that I think is solvable, but I'm not familiar enough with bower to understand how to do it.
In our project we have one particular dependency that needs to be modified slightly, as in probably 3 lines of code, to meet out project needs. Obviously it's not kosher to edit the file in bower_components directly, but this change needs to be made. What's the best way to go about doing this, and maintaining the dependency tree without having to commit the bower_components.
Understandably we'd have to make a sort of "local copy" of the dependency that we grabbed from Github initially. Any tips?
You could fork it and point to your fork instead or just clone it somewhere locally and point to the local repo.
I am using bower in a client-side project. Not all devs will have bower on their machine, so we need to include all bower dependencies in our source repo. But we are only allowed to check in the parts of the bower_components directory that are directly being used by the project (ie- only check in css/js/html files, and avoid checking in test, docs, etc).
Is there an existing script that can help with this, or do I need to manually go through and delete all unwanted pieces of bower components?
Unfortunately that's the only safe way you can do it, for now. The real solution is to encourage package authors to add unneeded files to the ignore property in their bower.json.