CODEWITHSUNDEEP
reactjswordpresspathgraphqlgatsby
TurboTobias
TurboTobias

Reputation: 625

Gatsby build path issues

Having issues running gatsby build with gatsby-starter-wordpress-advanced theme:

Error: ENOENT: no such file or directory, open 'C:\Users\Tobias\Desktop\Gatsby\gatsby-starter-wordpress-advanced\.template-cache\tmp-\.js'"

I figured this might be a problem with the path. The path should rather look like:

writing tmp-new-page/ template: open '.template-cache/tmp-new-page.js'

See repo: https://github.com/henrikwirth/gatsby-starter-wordpress-advanced/blob/master/create/utils.js

Line 53 you find the function createPageWithTemplate. I've tried console.log(page.uri) to see what's going on. It outputs the filename correctly. I've also tried with gatsby clean to clear the cache. It seems to be some kind of backslash issue where the path comes with a \ .js at the end instead of sample-page.js:

no such file or directory, open 'C:\Users\Tobias\Desktop\Gatsby\gatsby-starter-wordpress-advanced\.template-cache\sample-page\.js'

Upvotes: 2

Views: 525

Answers (1)

TurboTobias
TurboTobias

Reputation: 625

The issue have been resolved. The problem was related to update in WPGraphQL WordPress plugin. Had to update the paths, because the page.uri is different in the newer versions of WPGraphQL. Before it was just: some-page now it is /some-page/.

Secondly in the page template creation process the theme was using the uri, therefore, this messed up the paths for the template files. This has been switched to page.slug instead now and some extra checks, to make sure the frontPage is not ending up producing a wrong path.

The master branch of the starter theme have been updated.

Upvotes: 1

Related Questions