nx: "Error: ENOENT: no such file or directory" for deleted file

Current Behavior

This is happens with 10.0.0-rc.0 (not sure if it is the same with v9 stable, maybe caused by new version?)

After moving a model (class or interface) from project to lib there is an error with npm start (and with other commands most probably as well) “Error: ENOENT: no such file or directory {{old location of the file}}”. The new model is used correctly from the typescript lib (generated lib with nx) and old file has no any references in code.

Expected Behavior

Should not be an error after file is removed in case it is not used in project source locally (it works correctly right after commit).

With a debugging trough node module I found that the core of the problem - file node_modules/@nrwl/workspace/src/core/hasher/file-hasher.js reads files not from local files but from git (and then as removed file is in git it is included and other functions tries to read it locally and crash because it is removed locally). I do not think it is expected behaviour, correct?

Steps to Reproduce

Create an angular app with nx based on angular.
Create a model (class or interface) somewhere inside main angular project src as a separate file (for example my-model.model.ts)
Commit changes (not sure if push is needed)
Create a library with nx generate @nrwl/workspace:library mylibrary
Move my-model.model.ts to mylibrary, change imports to use a model from lib and remove old my-model.model.ts
Run npm start or ng serve - and you should get an error related to removed file (logs are added below)

Failure Logs

Error: ENOENT: no such file or directory, open '/Users/my-user/PhpstormProjects/my-org/src/node/apps/main-app/src/app/core/store/models/entity.model.ts'
    at Object.openSync (fs.js:443:3)
    at Object.readFileSync (fs.js:343:35)
    at TypeScriptImportLocator.defaultFileRead [as fileRead] (/Users/my-user/PhpstormProjects/my-org/src/node/node_modules/@nrwl/workspace/src/core/file-utils.js:150:17)
    at TypeScriptImportLocator.fromFile (/Users/my-user/PhpstormProjects/my-org/src/node/node_modules/@nrwl/workspace/src/core/project-graph/build-dependencies/typescript-import-locator.js:21:30)
    at Object.values.forEach (/Users/my-user/PhpstormProjects/my-org/src/node/node_modules/@nrwl/workspace/src/core/project-graph/build-dependencies/explicit-project-dependencies.js:11:27)
    at Array.forEach (<anonymous>)
    at Object.keys.forEach (/Users/my-user/PhpstormProjects/my-org/src/node/node_modules/@nrwl/workspace/src/core/project-graph/build-dependencies/explicit-project-dependencies.js:10:44)
    at Array.forEach (<anonymous>)
    at buildExplicitTypeScriptDependencies (/Users/my-user/PhpstormProjects/my-org/src/node/node_modules/@nrwl/workspace/src/core/project-graph/build-dependencies/explicit-project-dependencies.js:9:30)
    at buildDependenciesFns.forEach (/Users/my-user/PhpstormProjects/my-org/src/node/node_modules/@nrwl/workspace/src/core/project-graph/project-graph.js:61:41)

Environment

@nrwl/angular : 10.0.0-rc.0 @nrwl/cli : 10.0.0-rc.0 @nrwl/cypress : 10.0.0-rc.0 @nrwl/eslint-plugin-nx : Not Found @nrwl/express : Not Found @nrwl/jest : 10.0.0-rc.0 @nrwl/linter : Not Found @nrwl/nest : Not Found @nrwl/next : Not Found @nrwl/node : Not Found @nrwl/react : Not Found @nrwl/schematics : Not Found @nrwl/tao : 10.0.0-rc.0 @nrwl/web : Not Found @nrwl/workspace : 10.0.0-rc.0 typescript : 3.9.7

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 27
Comments: 91 (11 by maintainers)

Commits related to this issue

feat: remove mongoose - every time schematics are generated I run into this issue: https://github.com/nrwl/nx/issues/3370 - I'll come back to this later when a workaround is found — committed to Exac/thomas-assessment by Exac 4 years ago

Most upvoted comments

SOLVED but unhappy with the outcome

I’ve deleted an angular component that was generated using the CLI. Im getting the same error now even when I try to run a different app in the workspace.

node v14.3.0 yarn 1.22.4 nx 10.0.0

From the docs “By default, Nx uses a local computation cache. The cache is stored in node_modules/.cache/nx. […] Nx stores the cached values only for a week, after which they are deleted. To clear the cache, delete the cache directory, and Nx will create a new one next time it tries to access it.”

I’ve manually deleted the ‘.cache/nx’ folder. No success I’ve manually deleted all node_modules folder and reinstalled. No success I’ve run multiple commands using --skip-nx-cache. No success I’ve changed the cacheDirectory. No success

As the fellow reporter stated, this is NOT related to NX caching inside node_modules.

Eventually, I committed my changes in git. After this, everything started working again.

Now what if I did not want to commit, Should we follow any specific process to delete or rename a file? Should we document this as Common Problems?

+41

sesteva on Jul 21, 2020

Problem still occurs in version 12.0.6.

Renaming, moving or deleting files leads to this issue. Committing the changes to the local git repository serves as a workaround.

+19

talbx on Apr 21, 2021

For anyone still experiencing this issue, check the workspace.json file. For me, there was a reference to the deleted folder in there. Removing the reference fixed it.

+17

abomadev on Apr 20, 2022

As this has been an ongoing request and not being addressed, I decided to open another ticket related to this bug here https://github.com/nrwl/nx/issues/6370

Hope this bug will finally get visibility and higher priority. @vsavkin and any NX maintainers (@FrozenPandaz?).

+10

kevinolivar on Jul 15, 2021

I did analyze the problem:

The problem is in @nrwl/workspace, in version 11:

It occurs when the nx root folder isn’t the git root folder (e.g. in a monorepo the nx root folder is a sub folder in the git tree).

When checking the project dependencies with the git hasher (git-hasher.js), git status is used to get the current changed/added/deleted files. The deleted files are removed from the complete file list (git ls), but there is the problem:

The list of files from get status is based on the root git folder, the files from git ls are based on the sub folder where nx is installed.

When fixed correctly it will also solve the issue with “Warning: Fell back to using ‘fs’ to identify ${f} as deleted. Please open an issue at https://github.com/nrwl/nx so we can investigate.”

==============================================

Looking at the current code: This issue should is fixed at 24/3/2021, and should be solved in version 12.0.0

+10

joepjoosten on Jun 10, 2021

+1 to reopening this issue, please. It is detrimental to developer workflows and this is reason enough to stop using the tool.

+10

ovaisoozeer on Jun 3, 2021

This issue has not resolved yet… Please reopen the issue

95th on Jul 1, 2021

@Bullsized it’s not upvoted because it’s not a solution it just avoiding the issue. We are looking for solutions here. The best would be if NRWL team would be willing to fix this issue. This is clearly a huge bug.

csimpi on Sep 15, 2021

I would just add that git commit is not a solution but a workaround. I encounter this issue daily and it’s quite annoying while doing refactorings in a codebase.

miluoshi on May 27, 2021

Try git stash and git stash pop. It work for me.

tung-yojee on May 6, 2021

Still happening on 11.5.2 (nx React) with @nrwl/workspace @11.5.2 after renaming a file.

I do not know a workaround. Even removing the NPM cache does not help at all.

@vsavkin Any suggestions?

philonor on Mar 31, 2021

I’m having the same issue @10.0.2, I tracked down to file-hasher/getHashesFromGit().
The allFiles() function returns an array containing both the old location and the new location for moved files. This only happens to files that are staged on git.

Repro steps

npx create-nx-workspace repro
cd repro
nx generate @nrwl/angular:app app1/app1
git add .
git commit -m "Message"
nx g remove app1/app1-e2e
nx g remove app1-app1
nx generate @nrwl/angular:app app1
git add .

Now, just run nx serve and a wild error appears.

Workaround

Just unstage the git files. ~~I spent almost 4 hours to discover this~~

mukaschultze on Jul 22, 2020

This is still an issue in "@nrwl/workspace": "12.6.0-rc.0". I do NOT have a monorepo as subfolder in a git folder. My root folder is the monorepo. git stash seems to work as a workaround as suggested. @joepjoosten @brandonroberts

vodouZoheviCleef on Jul 26, 2021

I have the same issue, the nrwl workspace is a sub folder in the git tree. Please reopen the issue, its important for the developer workflows to work with it.

“@angular/cli”: “^11.2.14”, “@nrwl/workspace”: “12.2.0”,

Kpt74 on Jul 8, 2021

Not working in 10.0.6

dtomaszewski on Jul 28, 2020

Folks, sorry about this. I fixed the issue in Nx 10.0.2.

If you can still reproduce the issue in 10.0.2, please provide a repo that I can take a loot at.

vsavkin on Jul 22, 2020

Still happening on 11.6.0 after deleting a file 😦

JakubPawlak on Apr 13, 2021

@vsavkin for scenario when some file is just removed it seems to be ok. But when I move file to other location (in my case from app to lib) - it is still the same error.

Simple way to replicate:

Move some .spec file into another directory and error appears

hudzenko on Jul 22, 2020

Same here, this is really strange behavior. I would not expect it is something related to git. Simple git commit fixed the case. I would strongly recommend addressing this issue as lots of developers have similar problems.

pawelczak on Nov 3, 2021

still happening in "@nrwl/workspace": "12.3.6". please re-open the issue @vsavkin

For me, it happens on a file rename that doesn’t exist in master. So, I created a component in a branch and commit it. then I rename the component file name. I can’t run serve anymore.,

fasidOnGit on Jul 15, 2021

@nrwl/cli v12.3.3 - problem persists, commit/stash fixes the issue

dmk1111 on May 19, 2021

I can still reproduce this on @nrwl/workspace 10.0.7.

Steps to reproduce:

Committed changes to package.json and yarn.lock (to update nrwl to 10.0.7)
Have uncommitted changes including a deleted (moved) file

cwhaught on Aug 5, 2020

Same for me.

"@angular/cli": "12.0.4",
"@nrwl/workspace": "12.3.6",

tomaszwawrzyniakit on Jun 15, 2021

Still happening on 11.6.0 after deleting a file 😦

Same version here. It happens whenever I rename or move a file or dir. I have to commit a incomplete work to continue working.

rodzappa on Apr 19, 2021

@mukaschultze could you try 10.0.4? Thank you!

vsavkin on Jul 23, 2020

Yes, happening very often. we are seeing it after we migrate to v12.

fasidOnGit on Jul 15, 2021

Nx use “git ls-tree HEAD -r” command for get list of files in last commit, then comparing this with actual state of repo, so from my point of view, if file is messing Nx need to skip this compare and sign module for rebuild.

hajekj14 on Jul 21, 2020

Same here, just migrated to 10.0.1 and then I renamed a module and I’m getting this now. Is there cache that we can manually invalidate to work around?

countravioli on Jul 21, 2020

Still getting this problem in nx v12 But this worked for me rm -r -f node_modules/ && rm package-lock.json && npm cache clean --force

lucasrgsilva on Nov 12, 2021

Why this ticket is closed, i still have this problem.

vrapalis on Jun 15, 2021

hey guuuuus, just fixed with the stash , try git stash , its work for me

AhmedHlaimi on Jan 16, 2021

Not working here in 10.0.6.

Only committing the file helps as workaround.

shinjucommunications on Jul 26, 2020

Same error for me after deleting a service.

Can confirm that it is likely related to hashing git files.

A potential workaround is to commit your changes on your local branch, or provide an older --base / --head

michael-golden on Jul 21, 2020

happening with v10 stable as well:

simple reproduction:

create new workspace via npx create-nx-workspace@latest with Angular app
run npm run lint
delete app.component.spec.ts
run npm run lint again
get error message

markgoho on Jul 20, 2020

for anyone still having issues:

renaming a file and having that over staging (git) was the issue, I commited the rename only and it’s OK now.

>  NX  Report complete - copy this into the issue template

  Node : 14.20.0
  OS   : darwin arm64
  npm  : 6.14.17

  nx : 12.9.0
  @nrwl/angular : Not Found
  @nrwl/cli : 12.9.0
  @nrwl/cypress : 12.9.0
  @nrwl/devkit : 12.9.0
  @nrwl/eslint-plugin-nx : 12.9.0
  @nrwl/express : Not Found
  @nrwl/jest : 12.9.0
  @nrwl/linter : 12.9.0
  @nrwl/nest : Not Found
  @nrwl/next : 12.9.0
  @nrwl/node : Not Found
  @nrwl/nx-cloud : 12.3.13
  @nrwl/react : 12.9.0
  @nrwl/schematics : Not Found
  @nrwl/tao : 12.9.0
  @nrwl/web : 12.9.0
  @nrwl/workspace : 12.9.0
  @nrwl/storybook : 12.9.0
  @nrwl/gatsby : Not Found
  typescript : 4.3.5

jmsalcido on Sep 28, 2022

Is this getting any traction?

jeserkin on Apr 2, 2022

Same issue as everyone else. Apple M1 silicon. And Windows 11

prodkt on Apr 1, 2022

Happens for me with 13.8.1. I moved file into another library. And now nx linter does not want to catch this. It keeps thinking the file is in old location. And even stash / commit does not help. Weird…

hudzenko on Feb 15, 2022

SOLVED but unhappy with the outcome

I’ve deleted an angular component that was generated using the CLI. Im getting the same error now even when I try to run a different app in the workspace.

node v14.3.0 yarn 1.22.4 nx 10.0.0

From the docs “By default, Nx uses a local computation cache. The cache is stored in node_modules/.cache/nx. […] Nx stores the cached values only for a week, after which they are deleted. To clear the cache, delete the cache directory, and Nx will create a new one next time it tries to access it.”

I’ve manually deleted the ‘.cache/nx’ folder. No success I’ve manually deleted all node_modules folder and reinstalled. No success I’ve run multiple commands using --skip-nx-cache. No success I’ve changed the cacheDirectory. No success

As the fellow reporter stated, this is NOT related to NX caching inside node_modules.

Eventually, I committed my changes in git. After this, everything started working again.

Now what if I did not want to commit, Should we follow any specific process to delete or rename a file? Should we document this as Common Problems?

Thank you!, You save my life 😄

duykieu on Oct 12, 2021

Same here, git commit helped, but I didn’t want it

haskelcurry on Jul 29, 2021

Happened once with me after moving a file to another folder. git commit then everything is fine.

rexebin on Apr 10, 2021

still happens on 10.4.4

the framework could be a bit more pro-active in delivering pre configured paths and lint rules for the project

after project creation lands

nhhockeyplayer on Dec 1, 2020

Same happens with nx 10.3.1 after deleting schematics template files and not committing.

floratmin on Oct 29, 2020

Still happening on nx 10.3.0

rrdlpl on Oct 22, 2020

Seems like the issue is gone for “@nrwl/workspace”: “10.0.7”

falkosch on Aug 3, 2020

had the same, tracked @nrwl/workspace->project-graph … etc etc … after a while i backed my changes with a commit

maybe you could add handling for staged files (marked as deleted, renamed, etc…)

steflen on Jul 21, 2020