Resolving "EISDIR: illegal operation on a directory" when using git worktrees with nx

  • You are using nx and you have created a new git worktree from a branch. 
  • You already run "npm i" to install all dependencies
  • Now you are seeing the following error when you try to serve your app


NX   EISDIR: illegal operation on a directory, lstat 'C:'


Root Cause

The nx remote cache. The remote cache has a reference to you local cache. When you switch you local cache still point to you main repository source. Your worktree is living under another folder. Nx tries to read the local cache but fails.

Run to see and details 

npx nx serve your-app --verbose


Solution

Skip the remote cache

npx nx serve your-app --skipRemoteCache

Comments

Post a Comment

Popular posts from this blog

What is Base, Local & Remote in Git merge

Image
When you use a merge tool for Git and you have conflicts you often see these three versions of a file. This is called the three-way-merge. BASE LOCAL REMOTE So what are these files exactly? Imagine you have a branch. While you're working on the code, someone else has already changed the code in the main branch. Now you'll have a conflict if you merge your code into the main branch. The picture above emphasizes the points that are involved into the merge. GREEN : The common anchestor of the change. This is the BASE. RED : Your changes to the code. This is the REMOTE. ORANGE : The code change of someone else. This is the LOCAL. BLUE : The end result file after the merge. Here a more detailed illustration: Sometimes you will fallback to a two-way merge e.g. in cases where you or the other part deleted a file. Some tools refer them as "ours" or "theirs" ours => LOCAL theirs => REMOTE CONFISUNG NAMES? I personally find the naming confusing because why the h...
Read more

Debug Azure Function locally with https on a custom domain

Image
Description If you want to deploy an Azure Function normally this endpoint is publicly available. Therefore you need to secure the connection to this endpoint at least with ssl. Before you deploy you also want to test the connection probably locally. The following steps should help you to setup a https connection to a local Azure Function. 1 STEP: Create a Self Signed Certificate via PowerShell Open Windows Terminal or PowerShell as an Administrator The following script will create a self signed certificate in the "Users" own certificate store with the password 12345 The script will also export the certificate as PFX to C:\server.pfx The domain for the certificate will be "debug-local.com" $cert = New-SelfSignedCertificate -DnsName "debug-local.com", "debug-local.com" -CertStoreLocation "cert:\LocalMachine\My" $myPwd = ConvertTo-SecureString -String "12345" -Force -AsPlainText Get-ChildItem -Path "cert:\localMachine\My...
Read more

NPM: Semantic Versioning Characters

Image
  Semantic Versioning Semantic versioning is a solution for the software management term of "Dependency Hell". A software usually depends on other software.  But usually the "other" software also depends also on other products. The illustration above shows a tree of dependencies. Like in the illustration, your software can depend on an other software in different versions. To resolve issues like not to install same dependency multiple times or install the latest version of a software, there is a need of standardized software dependecy management. Semantic versioning standard offers tools like npm or yarn to resolve such dependencies. 📗 BASICS A semantic version consists of three numbers seperated by a dot: 1.1.1 Major Release.Minor Release.Patch Release 🥇Major Release: 2 .1.1 You increase your version to a major release when  your code has breaking changes  the users of your software need to update their code, e.g an API change or sth else which has causes a major...
Read more