So this issue comes off the back of a deployment that I did this morning, which failed.
The failure, sadly, was due to:
The newest version of this package being incompatible to the version of Angular for which I'm running (10.2.6).
Me, not locking down my packages to the exact version but rather allowing a bit of flex with ^ in my package.json for this entry.
My assumptions that that any updates to the Dependent Version of Angular would require a Major package update.
Again, my assumption that this package followed some sort of Semantic Versioning (major . minor . patch)
Could you provide some sort of Insight into how you version this package? Perhaps it would be worthy of a section in your readme?
Furthermore, may I request that when you change the versions of the dependent packages in the future; that you use some sort of Semantic Versioning to indicate that you've made breaking changes to this package.
And I'd just like to also take the time to thank you and the other contributors for your work on this package. It's saved me a few hours. Sadly it's stolen a few too. However I really do appreciate the hard work and hope that you folks keep it up.
So this issue comes off the back of a deployment that I did this morning, which failed. The failure, sadly, was due to:
^in my package.json for this entry.major . minor . patch)Could you provide some sort of Insight into how you version this package? Perhaps it would be worthy of a section in your readme?
Furthermore, may I request that when you change the versions of the dependent packages in the future; that you use some sort of Semantic Versioning to indicate that you've made breaking changes to this package.
And I'd just like to also take the time to thank you and the other contributors for your work on this package. It's saved me a few hours. Sadly it's stolen a few too. However I really do appreciate the hard work and hope that you folks keep it up.