Node manifest file paths aren't created correctly

[KyleAMathews]

Preliminary 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

[tomasbillborn]

I also experience this in Gatsby Cloud.

The build logs for the preview has no errors in it.

What I can see in the console is shown in the attached image.

[KyleAMathews]

Ok, so maybe not a windows-specific error then

[TylerBarnes]

@tomasbillborn that's not an error actually :) those are logs we use to make it easy to debug the UI for customers, it should be 404ing there initially. Make sure you're on the latest version of gatsby and gatsby-source-contentful for it to generate manifest files for previews.

This still seems windows-specific to me

[tomasbillborn]

I am on latest versions.
It is not doing it initially it keeps retrying forever.

It is the same error in Gatsby Cloud I get as locally.

I am on Windows so locally that might hold up, but is the manifest files built run-time by me or serverside by Gatsby Cloud?

[TylerBarnes]

@tomasbillborn thanks for the additional info. Can you share your Gatsby Cloud dashboard link, either via email (tyler@gatsbyjs.com) or by opening a Gatsby Cloud support ticket? That will allow us to take look at your site on Gatsby Cloud and figure out what's going on.

[tomasbillborn]

Sent you the information to your email.

[TylerBarnes]

Hi @tomasbillborn, thanks for sharing that with me! I had a look, and I'm still investigating, but it appears you're on @next versions of Gatsby packages and somehow this is being resolved to an earlier version of gatsby on Gatsby Cloud (Gatsby version: 3.6.0-next.1, the earliest supported version is 3.13.0). Can you try adding the latest stable versions of packages to see if it will work on Gatsby Cloud?

It looks like we have 2 separate issues here:

• Windows support for the node manifest API is breaking
• Your site is resolving to an earlier version of Gatsby on Gatsby Cloud which doesn't support the content sync / node manifest API - which is why it hangs forever in the preview UI.

[tomasbillborn]

Hello again Tyler Great you are making some progress on this :) The package.json being used looks like this and as you can see the latest Gatsby is set. Is there some issue with how the package-lock file looks? Locally I am on node 14.7 and npm 6 when npm install is building it. Or do I understand you incorrect and it’s the Gatsby Cloud plug-in you are referring to? If not how can I do it differently when having this package.json? { "name": "rebel-and-bird", "description": "Rebel and Bird", "version": "0.0.1", "author": "Rebel and Bird", "dependencies": { ***@***.***/rich-text-types": "^14.1.2", "dotenv": "8.2.0", "framer-motion": "^4.1.17", "gatsby": "4.1.0-next.2", "gatsby-plugin-google-tagmanager": "4.1.0-next.0", "gatsby-plugin-image": "^2.0.0", "gatsby-plugin-less": "6.1.0-next.0", "gatsby-plugin-lunr": "1.5.2", "gatsby-plugin-manifest": "4.1.0-next.0", "gatsby-plugin-minify-classnames": "0.3.1", "gatsby-plugin-react-helmet": "5.1.0-next.0", "gatsby-plugin-robots-txt": "1.5.0", "gatsby-plugin-sharp": "^4.0.1", "gatsby-plugin-sitemap": "5.1.0-next.0", "gatsby-remark-copy-linked-files": "5.1.0-next.0", "gatsby-source-contentful": "6.1.0-next.2", "gatsby-transformer-remark": "5.1.0-next.0", "less": "3.13.0", "lodash": "4.17.15", "moment": "^2.24.0", "react": "17.0.2", "react-dom": "17.0.2", "react-helmet": "6.1.0", "react-intersection-observer": "^8.32.1", "whatwg-fetch": "3.0.0" }, "keywords": [ "gatsby" ], "license": "MIT", "scripts": { "build": "gatsby clean && gatsby build", "dev": "gatsby clean && gatsby develop --https", "ngrok": "gatsby clean && gatsby develop", "x": "rimraf node_modules" }, "devDependencies": { "rimraf": "3.0.0", "cross-env": "5.2.1", "devcert": "^1.1.2", "gatsby-plugin-ngrok-tunneling": "1.1.5", "ngrok": "^3.2.5" }, "repository": { "type": "git", "url": "https://to-add.com" }, "browserslist": [ "last 2 versions", "> 2%" ] } Best regards Tomas Billborn 2 nov. 2021 kl. 00:21 skrev Tyler Barnes ***@***.***>:  Hi @tomasbillborn<https://github.com/tomasbillborn>, thanks for sharing that with me! I had a look, and I'm still investigating, but it appears you're on @next versions of Gatsby packages and somehow this is being resolved to an earlier version of gatsby on Gatsby Cloud (Gatsby version: 3.6.0-next.1). Can you try adding the latest stable versions of packages to see if it will work on Gatsby Cloud? It looks like we have 2 separate issues here: * Windows support for the node manifest API is breaking * Your site is resolving to an earlier version of Gatsby on Gatsby Cloud which doesn't support the content sync / node manfiest API - which is why it hangs forever in the preview UI. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#33743 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAE63DY4YW363QXDGVUTMADUJ4OHVANCNFSM5HBJ3JCA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[KyleAMathews]

Try deleting your lock file and then running npm install again. That clears up problems generally. -- Kyle Mathews Blog: *http://bricolage.io <http://bricolage.io>* Twitter: http://twitter.com/kylemathews

…

On Mon, Nov 1, 2021 at 11:02 PM Tomas Billborn ***@***.***> wrote: Hello again Tyler Great you are making some progress on this :) The package.json being used looks like this and as you can see the latest Gatsby is set. Is there some issue with how the package-lock file looks? Locally I am on node 14.7 and npm 6 when npm install is building it. Or do I understand you incorrect and it’s the Gatsby Cloud plug-in you are referring to? If not how can I do it differently when having this package.json? { "name": "rebel-and-bird", "description": "Rebel and Bird", "version": "0.0.1", "author": "Rebel and Bird", "dependencies": { ***@***.***/rich-text-types": "^14.1.2", "dotenv": "8.2.0", "framer-motion": "^4.1.17", "gatsby": "4.1.0-next.2", "gatsby-plugin-google-tagmanager": "4.1.0-next.0", "gatsby-plugin-image": "^2.0.0", "gatsby-plugin-less": "6.1.0-next.0", "gatsby-plugin-lunr": "1.5.2", "gatsby-plugin-manifest": "4.1.0-next.0", "gatsby-plugin-minify-classnames": "0.3.1", "gatsby-plugin-react-helmet": "5.1.0-next.0", "gatsby-plugin-robots-txt": "1.5.0", "gatsby-plugin-sharp": "^4.0.1", "gatsby-plugin-sitemap": "5.1.0-next.0", "gatsby-remark-copy-linked-files": "5.1.0-next.0", "gatsby-source-contentful": "6.1.0-next.2", "gatsby-transformer-remark": "5.1.0-next.0", "less": "3.13.0", "lodash": "4.17.15", "moment": "^2.24.0", "react": "17.0.2", "react-dom": "17.0.2", "react-helmet": "6.1.0", "react-intersection-observer": "^8.32.1", "whatwg-fetch": "3.0.0" }, "keywords": [ "gatsby" ], "license": "MIT", "scripts": { "build": "gatsby clean && gatsby build", "dev": "gatsby clean && gatsby develop --https", "ngrok": "gatsby clean && gatsby develop", "x": "rimraf node_modules" }, "devDependencies": { "rimraf": "3.0.0", "cross-env": "5.2.1", "devcert": "^1.1.2", "gatsby-plugin-ngrok-tunneling": "1.1.5", "ngrok": "^3.2.5" }, "repository": { "type": "git", "url": "https://to-add.com" }, "browserslist": [ "last 2 versions", "> 2%" ] } Best regards Tomas Billborn 2 nov. 2021 kl. 00:21 skrev Tyler Barnes ***@***.***>:  Hi @tomasbillborn<https://github.com/tomasbillborn>, thanks for sharing that with me! I had a look, and I'm still investigating, but it appears you're on @next versions of Gatsby packages and somehow this is being resolved to an earlier version of gatsby on Gatsby Cloud (Gatsby version: 3.6.0-next.1). Can you try adding the latest stable versions of packages to see if it will work on Gatsby Cloud? It looks like we have 2 separate issues here: * Windows support for the node manifest API is breaking * Your site is resolving to an earlier version of Gatsby on Gatsby Cloud which doesn't support the content sync / node manfiest API - which is why it hangs forever in the preview UI. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub< #33743 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AAE63DY4YW363QXDGVUTMADUJ4OHVANCNFSM5HBJ3JCA>. Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#33743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAARLB6FOP42PKF33PEHKD3UJ55H3ANCNFSM5HBJ3JCA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[tomasbillborn]

I deleted all node modules, cleared the cache, deleted the package-lock.json so this should now be updated.

[TylerBarnes]

Thanks @tomasbillborn ! I see it's updated in your dev site and I see some logs related to Content Sync there now 👍 have you been able to try it out from the Contentful side and see if it's working?

btw I'm working on resolving the windows issue today.

[tomasbillborn]

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 :)

[TylerBarnes]

@tomasbillborn sorry for the broken experience here! We're aware of that issue as well and are working with Contentful to fix it here contentful/apps#576. A PR was merged this morning which broke the Contentful Gatsby App for Content Sync. We'll be moving the Contentful Gatsby app to our own repo so we have more control over making quick fixes like that in the future.

[tomasbillborn]

@TylerBarnes now the Gatsby Cloud App works in Contentful, but the user experince is very bad compared to before.

If I use the previous implementation I instantly get the preview page loaded then I see the loader on the side.

This implementation takes about 15 - 20 sec to find the correct file and then show the preview page.

I also saw "gatsby-source-contentful": "6.2.0-next.0" was available so I upgraded to it, but I still get the same build error from the preview api (on Windows).

[TylerBarnes]

Thanks for the feedback @tomasbillborn! It's definitely slower but there are many benefits to it:

• Content authors know when builds fail because the UI shows an error. This means they don't have to wait for a long time and then ask a developer why their preview never showed up. They'll know right away that something isn't working.
• Any contentful entity at any level can be previewed, not just entities that have a direct correlation to a page. So any child entities or referenced entities which have no direct correlation to a page can be previewed if they're queried somewhere on a page in the Gatsby site.
• It works for all content types with no slug configuration in contentful
• Brand new pages don't display a 404 when initially opening the preview if the build hasn't completed yet.

We will also be working to speed it up and improve it over time.

[jackonawalk]

@tomasbillborn if you delete the Content Sync URL from your Gatsby Cloud app config in Contentful, Open Preview will fallback to the prior functionality.