Closed jnarowski closed 6 years ago
I see you answered this in another thread.
Just dropping a link to that thread here in case anyone else finds this. 🙂
yarn upgrade-interactive --latest
@stuta Yes, that's always to be expected with beta software, which is why the dependency ranges in package.json
for beta packages are locked. If you decide to manually upgrade beyond what the latest version of this boilerplate supports, you unfortunately have to be prepared to deal with any resulting breakages.
Yes, I very well undrestand this, I'm not complaining. It was just a warning that next update will break things.
Any thoughts as to how one might keep up with dependencies, once the boilerplate is applied to a project? I am using it in a production app, but would love to keep it as close to in-sync with what you have here, especially the fixes and improvements!