Ошибка enoent no such file or directory

Web development has come a long way now. Instead of using simple HTML/CSS, Javascript and PHP to build websites, developers now can choose from plenty of web development frameworks and server tools that make the job easier. 

In this article, we’re looking at the “enoent: no such file or directory” error when running Node.js web servers, its causes and what you can do to fix the problem.

---

What causes this error?

As the error message describes, the problem is caused by a missing configuration file or other dependencies required for your website or web app to run properly. 

Other possible causes include the following:

• Incorrect file paths for web server configuration files. 
• NPM configuration folders aren’t made.

Also read: Fix: An unexpected error is keeping you from copying the file

---

How to fix this?

Here are five fixes you can try out. 

Restart your PC

A quick and simple fix for the problem is to restart your PC. This ensures that any missing processes start up correctly alongside your operating system and that everything is in order before running your project.

---

Create an NPM directory

One of the main reasons you’d run into this error is that NPM doesn’t have a configuration directory to keep track of your project’s dependencies. 

The simplest way to fix this is to run the npm install command. If that doesn’t work, you can also try running npm update. Running both commands back to back can also sometimes fix the problem. 

Also read: Docs.google.com refused to connect: 6 Fixes

---

Check your configuration files

Take a good look at the directory that the error message shows. The file at the end is the missing dependency that’s causing this problem. While it can be any of the dependencies in your project, this is often a missing configuration file. 

To resolve the error, you can manually create the mentioned file path with the specified file at the end. Do keep in mind that while it might fix the problem we’re dealing with in this article, it can give you additional errors, as the resulting file will be empty. 

You can then work your way around the new error, if any, by installing any required packages that might be missing from your project. 

---

Fix the file path

As an extension to the last solution, you can also try and manually fix the file path that the error has reported missing. The specific way to do this varies from framework to framework, so you’ll have to look up the documentation of your specific framework in use to check how to modify file paths.

If you’re sure that the configuration file or dependencies exist, you can manually point your web server to the right file. 

---

Reinitialise your project

You also might have to reinitialise your project to freshen up all the dependencies you’re using. This can be done by deleting the node_modules folder and the package-lock.json file. Just open a terminal, head over to your project’s root folder and run the following commands one at a time.

rm -rf node_modules package-lock.json
npm install

If you get an error saying you don’t have appropriate permissions to carry out these tasks, prefix sudo to both commands. 

Also read: Fix: Unknown error: soap-error: encoding: object has no uirequestid property

The “enoent” can appear because of some missing files or usage of the relative path that can be solved by creating an expected directory structure or using an absolute path, respectively. There are also many other reasons for getting this error. This article contains all those causes and solutions with developers’ tips to solve the error quickly. So keep reading this article till the end to learn what is necessary to fix this error.

What Are the Causes of Getting “Enoent” Error Messages?

To solve the “enoent” error message, we first need to understand why this error appears. Let’s find out some of the common causes of this error.

– Starting the Node Server

This error can appear while starting the node server. This can happen because of the no existence of some important files at the expected location.

– Using a File Path Starting at the Directory Where the Script Was Executing

You can get this error if you use a file path that starts at the directory where scripts are executing but not at the project’s root.

– Having Another Console Windows

You can face this error if you have another conarele windows open that is running the app, and you try to re-run yarn to start in another console window.

– Having No Layout Folder

Having no layout folder can also be one of the causes here.

– Sudo Command

Anything wrong is the Sudo command or not running the sudo command will not allow you to write to /private/var/folders on mac, and this error appears.

– Wrong Path in Angular.json

A prevalent cause of this error is providing the wrong file path in angular.json, where you can fix the path to remove the error.

– Switching Git Branch

This error can appear if you switch from one git branch to another. The latter happened because some old files remained in the scripts inside the “node_module/.cache” directory.

– The angular.json File Doesn’t Have the “Styles” and “Scripts” Array.

If you are working in Angular 12 or above, and your angular.json file doesn’t have the “styles” and “scripts” arrays, you can also get this error in that condition.

– Typescript

If you are working on typescript, the JS will find the HTML file in the transpiled-JS folder. And if your HTML file is not present there, you will see the error.

– Mismatched Node Version

If you have installed the mismatch node version, you would probably get the error. You just need to install the correct node version via nvm to eliminate this error.

– Express.JS

If you are working with express.js and getting the same error, this could be because the current working directory might be the project’s root directory. You might be trying to read the file located in the script’s directory, and in this case, you might not run the file as a process.cwd() !==__dirname. This out and do the console log process.cwd() in the script you attempt to read JSON file.

– Getting Script-webpack-Plugin Error Message Along With Enoent Error

In some cases, you might get the script-webpack-plugin error and enoent value error. That could be because of the wrong path. You can get both of these errors on node.js or angular.

– Delete Some CSS Files

If you are working in CSS, you can face this error, have mistakenly deleted some critical CSS files and then copied them back.

– Using a Relative Path

If you are working on an API and some request, you might be using a relative path if you get this error with a message that it can’t read a path that doesn’t exist.

– Node Script

You can get this error while working with Node script and trying to transfer the files in use. Though most of the time, the error appears because of the files and folders that do not exist, you might experience that when you are close the chrome, the error gets removed.

It is happening because there is a symbolic link named RunningChromeVersion whose target doesn’t exist. The Node script doesn’t give any special treatment to links, so the default action is to follow the link when you try to open them. Like’s target doesn’t exist because it is not supposed to point to a file. It’s a dummy link with unrelated information like the version number stored in the “target” field where a file goes typically.

We discovered many causes of this error; let’s find out the solutions

– Starting the Node Server

If you are getting this error while starting the enoent nodejs server, there might be a need for some essential files not present in the expected location. If this is the case, you would see that it complained about missing a file. That is why, you need to create the expected directory structure. You can also configure the application you are working on to look in the correct directory.

If it is still not solved, go to the basics, and install enoent npm. If the problem is not solved yet, go for “npm update,” and then try “npm install.”

Using the “npm install,” a “node_module” directory in the current path will be created, the location where it is executed. When you use the “file server system module,” the below declaration will locate files from the “node modules,” a top-level directory.

const fs = require(‘fs’)

– Using a File Path Starting at the Directory Where the Script Was Executing

The simple and quick solution, in this case, is to use the below path while calling.

fs.createReadStream(‘scriptFolder/users.csv’)

– Having Another Console Windows

If you are having another console open and facing this issue, what happens is that as the first yarn executes, it prevents the second yarn from writing. As a solution, you can simply kill the first process, and you see it will work.

– Having No Layout Folder

If you don’t have a layout folder for your routine, you can use the enoent code below.

app.get(‘/’, (req,res)=>{
res.render(‘FolderName’, {layout: false});
})

Just change “FolderName” with your folder name, and your problem will be fixed.

– Sudo Command

To solve this issue, you need to follow some steps.

In the first step, you need to be in the app directory created by the following command.

npx create-react-app [app-name]

Then run the following

sudo npm install

To make it install all dependencies from the following

package.json

And then run the following

sudo npm start

Here you need to ensure that you run them with Sudo commands, which sometimes becomes indispensable.

– Switching Git Branch

If the issue is created because of switching between git branches, then you should delete “node_modules,” “build” directories, and “package-lock.json” files, and then you can issue the “npm install” command to fix the issue.

– The angular.json File Doesn’t Have the “Styles” and “Scripts” Array

If you are facing this issue because your angular.json file doesn’t have the “styles” and “scripts” arrays, you can add them to fix the problem. Those arrays are as follows:

“Styles”: [
“src/styles.css,”
“./node_modules/bootstrap/dist/css/bootstrap.css”
],
“Scripts”: [
“node_modules/jquerry/dist/jquerry.min.js”,
“node_modules/bootstrap/dist/js/bootstrap.js”
]

In the end, press CTRL+C and then ng serve.

– Typescript

If you are getting the error because the JS is not finding the HTML file in the transpiled-JS folder, you need to copy the file into the transpiled-JS folder where it should be located so that the JS can see the HTML file.

– Express.js

If you are working with express.js and getting this error, you should change the path to the following:

Const fs = require(‘fs’);
fs.readFileSync(‘${__dirname}\FILENAME’);

– Getting Script-webpack-Plugin Error Message Along With Enoent Error

If you are getting the script-webpack-plugin error message along with an enoent error, the cause for this error could be the wrong path. You first need to make sure the file path is correct in the angular.JSON file.

“Scripts”: [
“node_modules/jquery/dist/jquery/min.js”,
“node_modules/bootstrap/dist/js/bootstrap.js”
],

And then copy this and rerun the project.

You should also check the file path relative to the angular.json configuration file. You might have to add the root folder name as well.

– Delete Some CSS Files

If you are getting this error because of deleting some CSS files first and then copying them, you should restart your docker and other servers to remove the error.

– Using a Relative Path

If you are choosing a relative path, in this case, you are going to get this error. So to avoid the error, you should select the absolute path. And if your problem is still not solved, you can check the body—path value.

– Node Script

As a solution, you can use the Node equivalent of the lstat() to make sure whether the path is a symlink avoid transferring it in the same way. If you want to read the ‘target’ field, you can use readlink(). You should skip the symlinks while recursive file researching because it is possible that if you follow the symlink, you might get into the infinite loop.

FAQs

– What Is the Enoent?

The enoent meaning error no entry. This is used for more than files or dictionaries.

– What Does Enoent: No Such File or Directory Mean?

No such files or directory means that the library is currently needed or the executable binary doesn’t exist.

Conclusion

Let’s review what we learned today:

• Some causes can lead you to this error, including starting the node server or using a file path starting at the directory where the script was executed.
• You must have all the essential files at the expected location; otherwise, you must create the expected directory structure to avoid this error.
• Don’t use the relative path rather than the absolute path.

This article covered all the causes that can lead you to face the “enoent” error and their solutions. It’s time to meet this error with the help of this article and remove all the hurdles that stop you from coding.