Module not found – Error: Can't resolve deleted PAGE

[tujoworker]

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. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

The bug is related to the File Route API.

The same bug happens with yarn v1, v2 and v3.

Both the latest Gatsby version (v4.15) is effected, but also v2.9 has the same bug, with a different message. More info down below.

A minimal reproduction is given.

Reproduction Link

https://github.com/tujoworker/gatsby-file-route-api-bug

Steps to Reproduce

1. clone the repo.

2. run yarn

3. Start Gatsby by using the start script: yarn start

4. Duplicate src/pages/folder/. Give the page a new name,
   e.g. src/pages/folder-copy/. Everything is fine.

5. Delete src/pages/folder-copy/ again.

6. Enter another file in the repo (within your code editor), e.g.
   src/pages/index.js and hit save.

7. The error message:

Module not found: Error: Can't resolve './../../../src/pages/folder-copy/index.js' in '/dev/gatsby-filerouteapi-bug/.cache/this_is_virtual_fs_path/$virtual'
```

Expected Result

To delete the stale page(s). No error messages.

Actual Result

Module not found: Error: Can't resolve './../../../src/pages/folder-copy/index.js' in '/dev/gatsby-filerouteapi-bug/.cache/this_is_virtual_fs_path/$virtual'

In v2 the error message is:

gatsby-file-route-api-bug/src/pages/folder-copy/index.js File:
/gatsby-file-route-api-bug/src/pages/folder-copy/index.js

Environment

System:
    OS: macOS 12.0.1
    CPU: (10) x64 Apple M1 Pro
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.18.1 - /private/var/folders/6b/1cnty5gx3xv28k5fbrlyq
g140000gn/T/xfs-2547bb34/node
    Yarn: 3.1.0 - /private/var/folders/6b/1cnty5gx3xv28k5fbrlyqg1
40000gn/T/xfs-2547bb34/yarn
    npm: 8.1.0 - ~/.volta/tools/image/npm/8.1.0/bin/npm
  Languages:
    Python: 2.7.18 - /usr/bin/python
  Browsers:
    Chrome: 96.0.4664.45
    Edge: 95.0.1020.53
    Firefox: 88.0
    Safari: 15.1
  npmPackages:
    gatsby: ^4.2.0 => 4.2.0

Config Flags

No response

[njbmartin]

Does the issue still occur when you use gatsby clean?

[tujoworker]

@njbmartin yes. I mean, no. When running build or clean, everything is ok. This issue accrues during development, and it’s also why this is an issue. Renaming a file system page (path) including a folder (directory) name change should work without throwing an error.

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[tujoworker]

Let me check it out on v4 ✨

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[graysonhicks]

@tujoworker Are you still able to reproduce this?

[tujoworker]

@garethpbk Yes. I updated the reproduction repo to v4.2 – the thing is, once a directory/folder gets deleted , Gatsby (in development) does not recognize that it gets deleted.

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[tujoworker]

Hey you, robot – we shouldn’t close this yet.