feat(gatsby-source-wordpress): use gatsby-source-filesystem for remote file

[wardpeet]

Description

Use gatsby-source-filesystem for create-remote-file-nodes. We added multiple retry mechanism when the server wasn't responding and fixed couple of bugs to reduce spam to the server.
Moving back to this module, fixed the issue I was locally getting to fetch file nodes.

I published an alpha version of this gatsby-source-wordpress@alpha-wp-fileystem

Documentation

Related Issues

[TylerBarnes]

Hey @wardpeet ! Thanks for this! Unfortunately this will cause a few problems because of modifications I made to this copy of create-remote-file-node 🤦 See this PR for a temporary fix #29813

The retry code here was swallowing the error you were getting which is that this copy of create-remote-file-node was importing an export that no longer exists in gatsby-source-filesystem (createProgress). The PR above temporarily fixes it (I'll be working on using the official create-remote-file-node asap after that's merged).

I need to PR some changes / fixes to create-remote-file-node before this plugin can use it - there is a caching bug in it when you retry the same request later - if a request fails in create-remote-file-node and then you externally retry it later, it's promise will never resolve and it'll freeze the build process in some cases because the request cache in that helper doesn't delete from the cache when the request fails. I also have some logic where I'm awaiting a promise elsewhere in the WP plugin that gets resolved in this helper - and my copy of that helper is wiring up a plugin option to request concurrency in the copy of the helper. It's a bit messy unfortunately but I'll be fixing it soon 👍 The mistake here is that I intended to PR fixes to create-remote-file-node a while ago and forgot while I was working on the WP plugin 🤦