Version 1.1.2 uses all-lowercase file naming as opposed to previously used camel-case naming convention

[alex-signature-it]

Version 1.1.2 uses all-lowercase file naming as opposed to previously used camel-case naming convention

[victorb]

Hm, tricky. Npm forced me recently to update my package to only have
lowercase characters in my package name and seems like bower doesn't like
those changes. Not sure I can see a good solution to this. Anyone?
On Aug 13, 2015 17:02, "Alex Andrienko" [email protected] wrote:

Previous versions used to follow camel-case naming convention for the
files, e.g. ng_P_rogress/build/ng_P_rogress.js, and now it's
ng_p_rogress/build/ng_p_rogress.js.

It gets rather confusing/broken if upgraded via bower on a case-sensitive
file system, since it'll keep the old camel-case-named files next to new
lowercase ones and you might assume you've got a new version while your
website will be actually using an old one.

—
Reply to this email directly or view it on GitHub
#78.

[alex-signature-it]

Oh well, if that's intended or forced by the tools change I guess we'll have to live with it.
Thought it was just a typo of sorts.