Closed ghost closed 10 years ago
I won't drop the version from the library file name for convenience. And I don't advise you to load any library regardless of its version number, it may break your application too. Maybe bower has a grained loader like composer's?
However, I could make my Gruntfile create one more minified version without the version number, but we should think if it's really the solution.
Hello @pyrsmk,
You're right about retro-compatibility issues on version changes.
But a specific task that would produce a "generic" minified version would do the trick. Bower does manage versions (based on the repo's tags), so one keeps a hand on specific versions to install. Then the script path can remain generic (this one will never break).
Anyway, that issue really is out of curiosity (about how to avoid manual changes in the long run).
You're right, I forgot that bower manages versioning by git tags. Then, I think I could do the trick. It will take a moment to do because I'll need to update all my JS repos ;)
Fixed. I finally chose to completely remove version number from my minified files ^^
Wouldn't it be better to name the minified file without a specific version? Currently, when installing via bower, it's typically included that way:
As a dependency, its version may change some day and break that inclusion. Having the file called
toast.min.js
would avoid that.Possibly the version could be prepended as a commentary to the minified source.