I'm working on adding PWA support to open-tacos, and today I suddenly noticed the deployment wasn't actually building the PWA, while locally it still worked. After looking around, it turned out the new update (5.6.0) has a breaking change to the config. Since according to semver minor updates should be backwards compatible, package managers will automatically grab the latest (broken) version.
Versions
next-pwa: 5.5.4 & 5.6.0
next: 12.1.7-canary.48
How To Reproduce
Steps to reproduce the behavior:
Configure a project for next-pwa 5.5.4
Do a fresh install of all packages (which will install 5.6.0)
PWA isn't included in the build
Expected Behaviors
I expect the package to be backwards compatible between minor versions
Summary
I'm working on adding PWA support to open-tacos, and today I suddenly noticed the deployment wasn't actually building the PWA, while locally it still worked. After looking around, it turned out the new update (5.6.0) has a breaking change to the config. Since according to semver minor updates should be backwards compatible, package managers will automatically grab the latest (broken) version.
Versions
next-pwa
: 5.5.4 & 5.6.0next
: 12.1.7-canary.48How To Reproduce
Steps to reproduce the behavior:
next-pwa
5.5.4Expected Behaviors
I expect the package to be backwards compatible between minor versions