Node manifest file paths aren't created correctly
See original GitHub issuePreliminary Checks
- This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
- This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
Description
Report from Disco
rd
Reproduction Link
n/a
Steps to Reproduce
n/a
Expected Result
n/a
Actual Result
n/a
Environment
windows
Config Flags
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Gulp Rev doesn't include paths in my manifest file
I was having the same issue, and ended up renaming the asset dirs in the stream to what I wanted and specifying the...
Read more >App Manifest Attribute Reference | Cloud Foundry Docs
Each route for this app is created if it does not already exist. This attribute is a combination of push options that include...
Read more >Additional folders needed for path when running build ...
I've recently tried to use the build property of the manifest.json file which can execute a file when the plugin is published.
Read more >Add a web app manifest
The web app manifest is a simple JSON file that tells the browser about your web application and how it should behave when...
Read more >manifest.mf class-path not being read when executing jar file.
it works fine, and the debug statement reports the directory correctly. I've tried all kinds of variations of ./lib/ lib/ etcbut I never...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@tomasbillborn if you delete the Content Sync URL from your Gatsby Cloud app config in Contentful, Open Preview will fallback to the prior functionality.
Actually for some reason now when both preview webhook and content sync is set, Gatsby Cloud App (in Contentful) throws an error that the preview webhook url is not set (very frustrating).
Had a collegue test it too and he got the same result so I removed the content sync url and fallbacked on previous solution and it is at least working.
I hope this some temp bug they will fix soon. I will get back to you as soon as I can test it.
And great news about the windows bug 😃