Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gatsby-plugin-manifest 2.0.28 no longer generates manifest.webmanifest #13264

Closed
pgilad opened this issue Apr 10, 2019 · 5 comments · Fixed by #13271
Closed

gatsby-plugin-manifest 2.0.28 no longer generates manifest.webmanifest #13264

pgilad opened this issue Apr 10, 2019 · 5 comments · Fixed by #13271

Comments

@pgilad
Copy link
Contributor

pgilad commented Apr 10, 2019

Looks like something has changed with the plugin and it no longer generates the public/manifest.webmanifest file, causing deployments to be messed up 😢

% npx gatsby info

  System:
    OS: macOS 10.14.4
    CPU: (4) x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
    Shell: 3.0.2 - /usr/local/bin/fish
  Binaries:
    Node: 11.13.0 - ~/.nvm/versions/node/v11.13.0/bin/node
    npm: 6.9.0 - ~/.nvm/versions/node/v11.13.0/bin/npm
  Languages:
    Python: 2.7.16 - /usr/local/bin/python
  Browsers:
    Chrome: 73.0.3683.103
    Firefox: 66.0
    Safari: 12.1
  npmPackages:
    gatsby: ^2.3.16 => 2.3.16
    gatsby-cli: ^2.5.6 => 2.5.6
    gatsby-image: ^2.0.37 => 2.0.37
    gatsby-plugin-canonical-urls: ^2.0.12 => 2.0.12
    gatsby-plugin-catch-links: ^2.0.13 => 2.0.13
    gatsby-plugin-feed: ^2.1.0 => 2.1.0
    gatsby-plugin-google-analytics: ^2.0.18 => 2.0.18
    gatsby-plugin-manifest: ^2.0.28 => 2.0.28
    gatsby-plugin-netlify: ^2.0.13 => 2.0.13
    gatsby-plugin-offline: ^2.0.25 => 2.0.25
    gatsby-plugin-react-helmet: ^3.0.12 => 3.0.12
    gatsby-plugin-robots-txt: ^1.4.0 => 1.4.0
    gatsby-plugin-sharp: ^2.0.33 => 2.0.33
    gatsby-plugin-sitemap: ^2.0.12 => 2.0.12
    gatsby-plugin-typescript: ^2.0.12 => 2.0.12
    gatsby-remark-autolink-headers: ^2.0.16 => 2.0.16
    gatsby-remark-copy-linked-files: ^2.0.11 => 2.0.11
    gatsby-remark-embed-gist: ^1.1.7 => 1.1.7
    gatsby-remark-emojis: ^0.3.2 => 0.3.2
    gatsby-remark-images: ^3.0.10 => 3.0.10
    gatsby-remark-prismjs: ^3.2.8 => 3.2.8
    gatsby-source-filesystem: ^2.0.29 => 2.0.29
    gatsby-transformer-remark: ^2.3.8 => 2.3.8
    gatsby-transformer-sharp: ^2.1.17 => 2.1.17
@DSchau
Copy link
Contributor

DSchau commented Apr 10, 2019

Thanks for alerting us of this!

It looks like it was specifically introduced with 2.0.27, so if you pin to 2.0.26 you can restore the functionality.

Figuring out what the issue is--then will create a fix and publish as soon as possible. Thanks!

@pgilad
Copy link
Contributor Author

pgilad commented Apr 10, 2019

Thanks, that's exactly what I did for the time being!

@DSchau
Copy link
Contributor

DSchau commented Apr 10, 2019

It's this commit: 01670e18d02e08543b8c9e1742b3caa123e91b4e

Not really sure why yet!

@sidharthachatterjee
Copy link
Contributor

Fixed and published in [email protected]

@pgilad
Copy link
Contributor Author

pgilad commented Apr 10, 2019

Thanks! 🏆

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 a pull request may close this issue.

3 participants