5.0.0: Issues on Chrome 95

[frederikhors]

Describe the bug
Updating today from 4 to 5 and using the below simple command gives a manifest that Chrome 95 doesn't like:

To Reproduce
Steps to reproduce the behavior:

1. npx pwa-asset-generator ./src/icons/icon.svg ./static/icons/ --index ./src/index.html --manifest ./static/manifest.json --type png --icon-only --favicon --padding false

Generates this manifest.json:

{
  "name": "MyApp",
  "description": "MyApp",
  "short_name": "MyApp",
  "start_url": ".",
  "display": "standalone",
  "background_color": "#ffffff",
  "theme_color": "#333333",
  "icons": [
    {
      "src": "images/icons/manifest-icon-192.maskable.png",
      "sizes": "192x192",
      "type": "image/png",
      "purpose": "maskable"
    },
    {
      "src": "images/icons/manifest-icon-512.maskable.png",
      "sizes": "512x512",
      "type": "image/png",
      "purpose": "maskable"
    }
  ]
}

Expected behavior
I would like to have a default configuration to follow for no issues in Chrome.

System (please complete the following information):

• OS: win 10
• node version: 14
• npm version: 8.1.1
• cli version: 5.0.0

[mattostanik]

I had the same issue today. I changed purpose to "any maskable" in my manifest and that resolved the issue. But Chrome does now give me a warning that "any maskable" is discouraged.

[frederikhors]

I fixed it writing manually an entri in manifest icons array for any only. It should be create automatically I think.

[onderceylan]

Thanks for reporting this issue. As of latest changes on Chrome and Lighthouse audits,

• maskable any value is not recommended anymore.
• There should be at least one icon with the any purpose, or without the purpose altogether
• There should be at least oen icon with the maskable purpose

I'm working on a change to reflect this requirements update.

[onderceylan]

🎉 This issue has been resolved in version 6.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀