Skip to content

fix: staging package.json version and SW cache error handling#15

Merged
eurobuddha merged 1 commit intomasterfrom
fix/build-win-version-staging-sw-cache-error
Mar 23, 2026
Merged

fix: staging package.json version and SW cache error handling#15
eurobuddha merged 1 commit intomasterfrom
fix/build-win-version-staging-sw-cache-error

Conversation

@eurobuddha
Copy link
Copy Markdown
Owner

Summary

  • build/build-win.sh: staging package.json heredoc changed from single-quoted (<< 'PKGJSON') to unquoted (<< PKGJSON) so ${VERSION} expands — was hardcoded 0.4.8, will now always track the script's VERSION variable
  • template/shop/sw.js: .catch() added to caches.open() in fetch handler so cache quota or storage errors surface as a console warning instead of being silently swallowed

Test plan

  • Run npm run build:win and confirm the staged package.json contains "version": "0.5.0"
  • Confirm SW still caches assets normally; no console warnings under normal conditions

🤖 Generated with Claude Code

- build-win.sh: switch staging package.json heredoc to unquoted so
  ${VERSION} expands correctly — was hardcoded 0.4.8, now tracks VERSION
- sw.js: add .catch() to caches.open() in fetch handler so cache quota
  errors are logged rather than silently swallowed

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@eurobuddha eurobuddha merged commit 8e5d025 into master Mar 23, 2026
5 checks passed
@eurobuddha eurobuddha deleted the fix/build-win-version-staging-sw-cache-error branch March 23, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant