I was a bit surprised, as you probably will be too, as I did not expect bower to use the current bower configuration file, but the one corresponding to that version.
anyway, I already found what to do to fix it, just wanted you to be informed of the unexpected side effect.
P.S.: Don't judge me for still using bower 😛 , I will eventually move on to npm.
Hello!
Just wanted to inform you that https://github.com/aadsm/jsmediatags/commit/aab8bb0951f3b7c95aeb4a8e37b3f7e59b2c6653#diff-0a08a7565aba4405282251491979bb6b broke my build pipeline.
The culprit was the following line:
from my bower dependency file
I was a bit surprised, as you probably will be too, as I did not expect bower to use the current bower configuration file, but the one corresponding to that version.
anyway, I already found what to do to fix it, just wanted you to be informed of the unexpected side effect.
P.S.: Don't judge me for still using bower 😛 , I will eventually move on to npm.