-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Bower install not working #1897
Comments
Mh that is strange. Isn't bower working with npm packages? Are you using the latest version? |
I can confirm this issue. A temporary solution is to update bower.json: |
Version 5.5.1 also affected. Any solution? |
I'm going to fix this in the next few hours |
Solution / Workaround:Install dropzone with this command instead: You'll then need to adapt the links to dropzone to use Breakdown: I thought that bower was using I can go back and create tags for the older versions too if somebody needs a specific version, but other than that, please simply switch to the installation method I described above and upgrade to the latest version. |
IMHO it was a very bad decision to remove bower in patch release. You could tolerate bower until v6.0. |
@alexantr I didn't do it on purpose. I switched deployment systems, and there were a few major issues with legacy support with the library which is why I wanted to push a new patch release to address them. I hadn't counted on this issue to occur at the same time. In retrospect I should simply have pushed a major release, but I'm sure that that would have affected a lot of users as well. I have described a workaround for bower to get it to work again. |
Installing dropzone package with bower package manager is failing. i.e there is no dist folder after installing the package.
This started from today. I am guessing that this occurred due to the Master -> Main rename.
Is there a way to fix this quickly?
The text was updated successfully, but these errors were encountered: