Since adding a static asset, HMR fails and development mode stops working

[kripod]

Using Windows 10 x64 with Node 8, I encounter the issue below quite often while trying to change a file in development mode (gatsby develop). I'm not sure about the cause, but the issue started when I added an asset to the project's /static directory.

 I  Your site is running at http://localhost:8000
 I  Your graphql debugger is running at http://localhost:8000/___graphql
info changed file at C:\Development\Projects\mvk-web\src\pages\gallery.jsx
 WAIT  Compiling...                                                                 00:16:17
error Plugin dev-404-page returned an error


  Error: EPERM: operation not permitted, open 'C:\Development\Projects\mvk-web\.cache\dev-40  4-page.js'

  - copy-file-sync.js:23 copyFileSync
    [mvk-web]/[fs-extra]/lib/copy-sync/copy-file-sync.js:23:18

  - copy-sync.js:43 Object.copySync
    [mvk-web]/[fs-extra]/lib/copy-sync/copy-sync.js:43:5

  - gatsby-node.js:34 _callee$
    [mvk-web]/[gatsby]/dist/internal-plugins/dev-404-page/gatsby-node.js:34:18

  - gatsby-node.js:51 Object.createPages
    [mvk-web]/[gatsby]/dist/internal-plugins/dev-404-page/gatsby-node.js:51:18

  - api-runner-node.js:104 runAPI
    [mvk-web]/[gatsby]/dist/utils/api-runner-node.js:104:36

  - api-runner-node.js:178
    [mvk-web]/[gatsby]/dist/utils/api-runner-node.js:178:33

  - map.js:27
    [mvk-web]/[gatsby]/[async]/internal/map.js:27:9

  - eachOfLimit.js:64 replenish
    [mvk-web]/[gatsby]/[async]/internal/eachOfLimit.js:64:17


 ERROR  Failed to compile with 1 errors                                             00:16:18
 error  in ./.cache/dev-404-page.js

Module build failed: Error: ENOENT: no such file or directory, open 'C:\Development\Projects\mvk-web\.cache\dev-404-page.js'

 @ ./.cache/sync-requires.js 11:53-123

info changed file at C:\Development\Projects\mvk-web\src\pages\gallery.jsx
 WAIT  Compiling...                                                                 00:16:22
error There was a problem reading the file: C:/Development/Projects/mvk-web/.cache/dev-404-page.js


  Error: ENOENT: no such file or directory, open 'C:\Development\Projects\mvk-web\.cache\dev  -404-page.js'

 ERROR  Failed to compile with 1 errors                                             00:16:23
 error  in ./.cache/dev-404-page.js

Module build failed: Error: ENOENT: no such file or directory, open 'C:\Development\Projects\mvk-web\.cache\dev-404-page.js'

 @ ./.cache/sync-requires.js 11:53-123

Done in 94.08s.

[KyleAMathews]

Does the problem fix itself if you empty the static directory?

[KyleAMathews]

Oh this could be the problem jprichardson/node-fs-extra#320

[KyleAMathews]

Yeah I think we need to add the full path to the copy code here: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/utils/copy-static-directory.js

[KyleAMathews]

Could you test this and put together a PR if this fixes things?

[kripod]

Unfortunately, I’m currently not able to test it, but will do so as soon as possible. The project reproducing the issue can be found here.

[resir014]

Having the same issue here, running Windows 10 x64.

[kripod]

@KyleAMathews Unfortunately, your solution didn't work, but I figured out that the root cause of the problem is located here:

gatsby/packages/gatsby/src/internal-plugins/dev-404-page/gatsby-node.js

Line 11 in 524ff17

fs.copySync(currentPath, newPath)

Also, the following error message is shown for a tiny fraction of time on the frontend:

[KyleAMathews]

@kripod yeah it looks like newPath isn't being generated correctly — looks like it has a space somehow in it — could you debug why that is?

[kripod]

@KyleAMathews Actually, I just put some console.log instructions inside node_modules/gatsby/dist/internal-plugins/dev-404-page/gatsby-node.js, and it resulted in the following output:

info changed file at C:\Development\Projects\mvk-web\src\pages\gallery.jsx
 WAIT  Compiling...                                                                 01:01:33

currentPath: C:\Development\Projects\mvk-web\node_modules\gatsby\dist\internal-plugins\dev-404-page\raw_dev-404-page.js
newPath: C:\Development\Projects\mvk-web\.cache\dev-404-page.js
error Plugin dev-404-page returned an error


  Error: EPERM: operation not permitted, open 'C:\Development\Projects\mvk-web\.cache\dev-40  4-page.js'

  - copy-file-sync.js:23 copyFileSync
    [mvk-web]/[fs-extra]/lib/copy-sync/copy-file-sync.js:23:18

>

So, I think there's no weird space character in any of those variables.

[KyleAMathews]

There's two spaces in dev-40 4-page.js where it should be dev-404-page.js

[kripod]

Not sure how, because as you can see, I did the logging straight inside the aforementioned gatsby-node.js file, and I think the file copying operation happens just after logging.

[KyleAMathews]

I'm confused :-) I'm just looking at what you put into the issue. I can't replicate what you're seeing.

[kripod]

I can reproduce the issue using the following procedure:

1. Clone https://github.com/simonyiszk/mvk-web and run yarn
2. Run yarn develop
3. Navigate to http://localhost:8000/teams
4. Edit src/pages/teams.jsx, repeat until the issue reveals itself

[KyleAMathews]

This is on windows? Can you replicate this on other systems?

[kripod]

The issue happens since implementing i18n support based on the following guide: https://www.gatsbyjs.org/blog/2017-10-17-building-i18n-with-gatsby/

And yes, I'm on Windows 10, haven't tried replicating on other systems yet.

[kripod]

Oh, by the way, the additional 2 spaces were because of console output formatting (wrapping the remaining string to be on a new line with 2 spaces of padding).

[Michael-Brooks]

I too am getting this issue when upgrading to versions 1.9.110 and 1.9.112, but it doesn't happen with my current version of 1.9.45. I haven't tried any versions in between, but thought I would give the official starter version a go and the latest to compare.

[szhshp]

Got same issue, cleaned .cache and public/static which does no help. Win10 64b

[szhshp]

For my scenario, seems the file dev-404-page.js is not generated correctly.
It throws an error when changing the file.
Create it in .cache manually could be a temporary solution.

[KyleAMathews]

@szhielelp @Michael-Brooks the error seems to be windows specific — could you try debugging what's happening when the file copy fails? Would love a PR fixing things!

[kildareflare]

I'm also seeing this repeatably. I have added some code to gatsby-node to download files from remote urls in order to process them. This all appears to work fine. However intermixed within the file results is an error related to the dev 404 page. It appears that this file is created multiple times and the first few pass, when it fails I've narrowed it down to this line in fs-extra/copy-file-sync.js:

const fdw = fs.openSync(destFile, 'w', stat.mode)

The logs preceding this spit out

newPath C:\Code\Freelance\twobobs_gatsby\.cache\dev-404-page.js
fs-extra/copyFileSync
srcFile: C:\Code\Freelance\twobobs_gatsby\node_modules\gatsby\dist\internal-plugins\dev-404-page\raw_dev-404-page.js
destFile: C:\Code\Freelance\twobobs_gatsby\.cache\dev-404-page.js

But there is clearly a space coming in from somwhere as this is the error in the console

 EPERM: operation not permitted, open 'C:\Code\Freelance\twobobs_gatsby\  .cache\dev-404-page.js'

I'm also on Windows 10 64.
node 6.11.3
fs-extra 4.02
full results here: https://gist.github.com/kildareflare/754fee0e2c8002b28afb16464504981f

I've seen this (or similar) in the past, but right now it is only occurring when I try to process the images.
If I remove the file download code (below) from onCreateNode, I don't see it.

   console.log(`node.internal.owner: ${node.internal.owner}: ${node.type}`)

    let slideshow = node.data.slideshow;

    if(slideshow && slideshow.length > 0) {
      console.log(`download images: () ${slideshow.length})`);

      //pull down all images and store locally
      slideshow.forEach( (image) => {
        createRemoteFileNode({
          url: image.photo.url,
          store,
          cache,
          createNode
        }).then((result) => {
          console.log(`FILE RESULT ===================================================================================`)
          console.log(result)
        })
      });
      //then we need to process eachimage and replace the original with the new processed image html
    }
    }

I'll keep digging...

Question Should dev-404 be created more than once?

[kildareflare]

I have the same issue. also Windows 10 x64. Node 6.11.3.

I've traced it through and found the line causing the issue is

const fdw = fs.openSync(destFile, 'w', stat.mode)

in fs-extra/copy-file-sync.js.

I've seen this error before, but currently only getting it when running this code in onCreateNode.

      //pull down all images and store locally
      slideshow.forEach( (image) => {
        createRemoteFileNode({
          url: image.photo.url,
          store,
          cache,
          createNode
        }).then((result) => {
          console.log(`FILE RESULT ===================================================================================`)
          console.log(result)
        })
      });
      //then we need to process eachimage and replace the original with the new processed image html
    }

Full error log here: https://gist.github.com/kildareflare/754fee0e2c8002b28afb16464504981f

Log preceding the error spit out the following, which look OK

srcFile: C:\Code\twobobs_gatsby\node_modules\gatsby\dist\internal-plugins\dev-404-page\raw_dev-404-page.js
destFile: C:\Code\twobobs_gatsby\.cache\dev-404-page.js
destFile C:\Code\twobobs_gatsby\.cache\dev-404-page.js

But, the error message defeintly shows some extra spaces:

EPERM: operation not permitted, open 'C:\Code\twobobs_gatsby\  .cache\dev-404-page.js'

I've also noticed that when the error coccurs, the dev-404 page is created multiple times (see full log).
Whereas on runs that pass with no errors, the page is only created once.

Using fs-extra 4.0.2
Will keep digging.

[kildareflare]

Updated to node 8.9 and now get a bit more error detail

ERROR  Failed to compile with 1 errors14:42:36

This dependency was not found:

* C:\Code\twobobs_gatsby\.cache\dev-404-page.js in ./.cache/sync-requires.js
To install it, you can run: npm install --save C:\Code\twobobs_gatsby\.cache\dev-404-page.js

But that said, I've now noticed that lots of my error messages have weird gaps in them.

 Invariant Violation: Encountered an error trying to infer a GraphQL typ  e for: "data.slideshow.localFile___NODE". There is no corresponding node with   the id field matching: "C:/Code/twobobs_gatsby/.cache/gatsby-source-  filesystem/f81b92fa02888e16aae3362f6dca8d8d.jpg absPath of file"

[Magneticmagnum]

I'm also running into this problem on a Windows 10 x64 machine :(

[Magneticmagnum]

Forgot to add: Emptying images I use in the project from the static folder will compile correctly. I also have other files in my static folder that I don't import in my pages.

[kripod]

Unfortunately, I'm still getting errors even after removing the static directory, cleaning the cache and re-donwloading node_modules.

[kripod]

I just started a new Gatsby project and observed that the wrong behavior starts when I add an imageSharp object to a GraphQL query. I think that the bug might be related to gatsby-plugin-sharp.

[resir014]

@kripod Oddly enough, the problem exists for me even without gatsby-plugin-sharp.

[MaralS]

I'm facing to to same problem unfortunately. Anyone can help ?

[coulson84]

Unfortunately not - just npm installed 1.9.138 and still getting the same error :(

[coulson84]

Also on another unsurprising note the code change I mentioned above doesn't solve the problem. It just seems to reduce the chance of the issue showing.

[MaralS]

I tried to fix this issue with @coulson84 method but It didn't work. It's very frustrating.
When I encount this error, I have to stop with ctrl + c and run again yarn develop.

[KyleAMathews]

Does this happen on every Gatsby site for y'all? Or just certain ones? Could someone try installing various starters and testing this?

Also, it seems this is a windows-only issue but to double-check, has anyone seen this on Mac?

[MaralS]

@KyleAMathews I will try on my Mac

[MaralS]

@KyleAMathews I confirm that this issue is specific to Windows x64

[waywardm]

Im getting this error all the time on windows 64

ERROR Failed to compile with 1 errors 13:39:49
error in ./.cache/dev-404-page.js

Module build failed: Error: ENOENT: no such file or directory, open 'S:\gatsbysowerby.cache\dev-404-page.js'

@ ./.cache/sync-requires.js 15:53-106

info changed file at S:\gatsbysowerby\src\templates\business-listing.js
WAIT Compiling... 13:39:52
error There was a problem reading the file: S:/gatsbysowerby/.cache/dev-404-page.js

Error: ENOENT: no such file or directory, open 'S:\gatsbysowerby.cache\dev-404-page.js'

ERROR Failed to compile with 1 errors 13:39:52
error in ./.cache/dev-404-page.js

[waywardm]

Error: EPERM: operation not permitted, open 'S:\gatsbysowerby.cache\dev-404-page.js'

• copy-file-sync.js:23 copyFileSync
  [gatsbysowerby]/[fs-extra]/lib/copy-sync/copy-file-sync.js:23:18

• copy-sync.js:43 Object.copySync
  [gatsbysowerby]/[fs-extra]/lib/copy-sync/copy-sync.js:43:5

• gatsby-node.js:34 _callee$
  [gatsbysowerby]/[gatsby]/dist/internal-plugins/dev-404-page/gatsby-node.js:34:18

• gatsby-node.js:51 Object.createPages
  [gatsbysowerby]/[gatsby]/dist/internal-plugins/dev-404-page/gatsby-node.js:51:18

• api-runner-node.js:104 runAPI
  [gatsbysowerby]/[gatsby]/dist/utils/api-runner-node.js:104:36

• api-runner-node.js:178
  [gatsbysowerby]/[gatsby]/dist/utils/api-runner-node.js:178:33

• map.js:27
  [gatsbysowerby]/[gatsby]/[async]/internal/map.js:27:9

• eachOfLimit.js:64 replenish
  [gatsbysowerby]/[gatsby]/[async]/internal/eachOfLimit.js:64:17

• eachOfLimit.js:49 iterateeCallback
  [gatsbysowerby]/[gatsby]/[async]/internal/eachOfLimit.js:49:17

• onlyOnce.js:12
  [gatsbysowerby]/[gatsby]/[async]/internal/onlyOnce.js:12:16

• map.js:29
  [gatsbysowerby]/[gatsby]/[async]/internal/map.js:29:13

• util.js:16 tryCatcher
  [gatsbysowerby]/[bluebird]/js/release/util.js:16:23

• nodeify.js:23 Promise.successAdapter
  [gatsbysowerby]/[bluebird]/js/release/nodeify.js:23:30

• promise.js:566 Promise._settlePromise
  [gatsbysowerby]/[bluebird]/js/release/promise.js:566:21

ERROR Failed to compile with 1 errors 13:50:05
error in ./.cache/dev-404-page.js

Module build failed: Error: ENOENT: no such file or directory, open 'S:\gatsbysowerby.cache\dev-404-page.js'

[kripod]

@KyleAMathews Is there a chance this could get fixed by v2? Are there any plans to refactor the HMR code, or should we keep investigating the issue even before the release of v2?

[KyleAMathews]

@kripod would love to get this fixed but we still don't understand the underlying cause of the problem. It isn't something that needs to wait for v2. If you could investigate more to discover what's going wrong on windows, that'd be great!

[kripod]

I have already tried to find the reason once, but unfortunately, I couldn't. It's good to know that we should not expect a fix by v2, though.

[krachim]

Hi there,

i have the same error on Windows x64. I tried to figure out why, but got no more time. My findings so far:
I guess it´s kind of a timing problem. When add a Filter to check if dest file is there in
./node_modules/gatsby/dist/internal-plugins/dev-404-page/gatsby-node.js:

const filterFunc = (src, dest) => {
  fs.access( dest, fs.constants.R_OK | fs.constants.W_OK, err => {
      if (err) {
        console.log(err)
        return false
      } else {
        return true
      }
    }
  )
}

fs.copySync(currentPath, newPath, { filter: filterFunc })

it seems to work without any error occuring.

another quick and dirty workarround is to change copySync to copy.
fs.copySync(currentPath, newPath);
in
fs.copy(currentPath, newPath);

both seems to work for me ...

Hope this helps someone.
Have a nice Day!

[kripod]

@op3d Thank you for the suggestions, I highly appreciate your effort! Actually, I think that the first solution could be applied as a temporary measure, combined with a re-scheduler queue which can store the file operations to be done as soon as the files are available.

[kripod]

The first solution didn't work for me, but using fs.copy instead of fs.copySync seems to solve the problem.

@KyleAMathews Is there any reason against using fs.copy? Because if there isn't, then I think that mitigating this issue would greatly improve the developer experience for Windows users.

EDIT: While the frequency of failures has decreased, errors still get thrown, even with fs.copy.

[KyleAMathews]

@kripod yeah, definitely doesn't need to be copySync so if you think it helps, PR a change to fs.copy.

I guess it's kind of a timing problem. When add a Filter to check if dest file is there in

It's not a timing problem — the .cache directory always exists by the time the copy code is run. It's a permission issue that for some reason only crops up on windows.

[kripod]

@KyleAMathews What’s strange is that issue happens exclusively with internal-plugins/dev-404-page/gatsby-node.js. I remember that older versions of Gatsby didn’t have this issue. I think that the issue originates from the time between v1.9.25 and v1.9.45. A git blame may take us closer to a viable solution.

[waywardm]

many thanks for looking further into this issue @kripod As someone with not too much technical knowledge where exactly do i change it to fs.copy

[resir014]

@waywardm I'm currently applying the fixes suggested by @op3d @kripod and will put up a PR soon. Should be out in the next update.

[kripod]

I think I have fixed the issue for real, by changing the plugin loading order and awaiting fs.copy. I've tried to reproduce the bug with my fix in place, but couldn't. 😊

[waywardm]

@kripod i would be willing to test it now if you could tell me what code to replace as it is currently making the development process no fun

[kripod]

@waywardm If you are using a fairly new version of Node (e.g. v8.9.3, which I am currently using), you could test the fix by applying the following modifications:

• Replace the code inside node_modules/gatsby/dist/bootstrap/load-plugins.js with https://github.com/kripod/gatsby/blob/c8b50f71eba518c7c182d108964c80b970f485b6/packages/gatsby/src/bootstrap/load-plugins.js
• Replace the code inside node_modules/gatsby/dist/internal-plugins/dev-404-page/gatsby-node.js with https://github.com/kripod/gatsby/blob/c8b50f71eba518c7c182d108964c80b970f485b6/packages/gatsby/src/internal-plugins/dev-404-page/gatsby-node.js

Please give us feedback, it would be very valuable!

[waywardm]

@kripod

I can confirm the error has gone away, I do get one error but it doesn't prevent gatsby from compiling which is: (apologies for the long compile)

You can now view gatsby-starter-default in the browser.

http://localhost:8000/

View GraphiQL, an in-browser IDE, to explore your site's data and schema

http://localhost:8000/___graphql

Note that the development build is not optimized.
To create a production build, use gatsby build

WAIT Compiling... 12:48:42
DONE Compiled successfully in 333ms 12:48:43
info changed file at S:\gatsbysowerbymark\src\pages\businesses\academydivers.md
WAIT Compiling... 12:48:50

             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/diverlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/edenlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/barfranlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/chiropracticlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/calderhouselogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/cobblestoneslogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/coversurelogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/dariologo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/firehouselogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/Fresh-Fields-Twitter.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/gabrielslogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/gimbalslogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/happydayslogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/jcjoellogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/justpeachlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/metimelogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/simprintlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/dpautologo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/sprayme.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/syhibalogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/temujinlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/blindpiglogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/hobbitlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/thesaltroomlogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/thewharfcafe.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/TFIX-Twitter-Logo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.


             The requested width "400px" for a resolutions field for
             the file S:/gatsbysowerbymark/src/images/businesslogos/trinkettelogo.png
             was wider than the actual image width of 300px!
             If possible, replace the current image with a larger one.

Accomodation
Bars
Alternative Therapy Massage
Bakeries
Barbers
Beauticians
Butchers
Cafes
Cards and Gifts
Charity Shops
Coffee Shops
Chiropractors
Cycle Shops
Clothing
Diy Shops
Diving Tuition
Dentists
Delicatessens
Eating Out
Fashion
Estate Agents
Electrical Appliances
Hairdressers
Flower Shops
Hair Salons
Hardware Shops
null
Health
null
Insurance Brokers
Key Cutters
Jewellery
Lettings Agents
Manicurists
Market Stalls
Manufacturing
null
Pubs
Opticians
null
Retailers
Printers
Sandwich Shops
Shoe Repairers
Sound and Vision
null
null
Tyre Fitters
Televisions
Vacuum Repairs
Vehicle Bodywork
Vehicle Repairs
ERROR Failed to compile with 1 errors 12:48:52
error in ./.cache/pages.json

Syntax Error: Unexpected end of JSON input
at JSON.parse ()

@ ./.cache/root.js 26:13-36

WAIT Compiling... 12:48:52
DONE Compiled successfully in 457ms 12:48:52

admin@DESKTOP-HK27D9K MINGW64 /s/gatsbysowerbymark (master)

however i'm not sure if that is related

[clarkd]

I'm still seeing this issue on Windows:

PS C:\Users\Dave\Documents\Code Repository\docs> gatsby develop
success delete html and css files from previous builds — 0.718 s
success open and validate gatsby-config — 0.315 s
success copy gatsby files — 0.204 s
success onPreBootstrap — 1.985 s
success source and transform nodes — 2.446 s
success building schema — 1.551 s
success createLayouts — 0.050 s
success createPages — 0.746 s
error UNHANDLED REJECTION


  Error: EPERM: operation not permitted, open 'C:\Users\Dave\Documents\Code Repository\docs\.cache\dev-404-page.js'

Any ideas?

[Lelegithub]

Same error here, on Win10 x64 !
error There was a problem reading the file: C:/U***/gatsby-travel-website-v1/src/pages/destinationsf.js

Error: ENOENT: no such file or directory, open '