Npm err code enoent

03.09.202203.09.2022 admin 0 Comments

Npm err code enoent

How to read npm ENOENT errors

I’ve got 2 ENOENT errors. I know «ENOENT» means «Error NO ENTrance», but what exactly is missing in these two ENOENTs? What do these error messages mean? I would like to decipher them to be able to debug the problems.

One seems to have an «lstat» problem on gbk.js, the other an «chmod» problem on util.js, but what about the commands «node», «npm» and «install», «cwd», «fstream», and Object.oncomplete?

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Reading the error line: Error: ENOENT, lstat ‘/home/ubuntu/.npm/iconv-lite/0.2.11/package/encodings/table/gbk.js’

The rest are debug information. These all are some variables/properties at the time error happened:

These are about fstream module. It Indicates what was it doing exactly.

Common errors

Table of contents

Broken npm installation

If your npm is broken:

No compatible version found

\AppData\Roaming\npm’ on Windows 7 permalink» >

Error: ENOENT, stat ‘C:\Users\ \AppData\Roaming\npm’ on Windows 7

The error Error: ENOENT, stat ‘C:\Users\ \AppData\Roaming\npm’ on Windows 7 is a consequence of joyent/node#8141, and is an issue with the Node installer for Windows. The workaround is to ensure that C:\Users\ \AppData\Roaming\npm exists and is writable with your normal user account.

You are trying to install on a drive that either has no space, or has no permission to write.

You need to install git. Or, you may need to add your git information to your npm profile. You can do this from the command line or the website. For more information, see «Managing your profile settings».

Running a Vagrant box on Windows fails due to path length issues

@drmyersii went through what sounds like a lot of painful trial and error to come up with a working solution involving Windows long paths and some custom Vagrant configuration:

In the code above, I am appending \\?\ to the current directory absolute path. This will actually force the Windows API to allow an increase in the MAX_PATH variable (normally capped at 260). Read more about max path. This is happening during the sharedfolder creation which is intentionally handled by VBoxManage and not Vagrant’s «synced_folder» method. The last bit is pretty self-explanatory; we create the new shared folder and then make sure it’s mounted each time the machine is accessed or touched since Vagrant likes to reload its mounts/shared folders on each load.

npm only uses git: and ssh+git: URLs for GitHub repos, breaking proxies

I fixed this issue for several of my colleagues by running the following two commands:

You are trying to talk SSL to an unencrypted endpoint. More often than not, this is due to a proxy configuration error (see also this helpful, if dated, guide). In this case, you do not want to disable strict-ssl – you may need to set up a CA / CA file for use with your proxy, but it’s much better to take the time to figure that out than disabling SSL protection.

This problem will happen if you’re running Node 0.6. Please upgrade to node 0.8 or above. See this post for details.

You could also try these workarounds: npm config set ca «» or npm config set strict-ssl false

If this does not fix the problem, then you may have an SSL-intercepting proxy. (For example, https://github.com/npm/npm/issues/7439#issuecomment-76024878)

Not found / Server error

Many ENOENT / ENOTEMPTY errors in output

cb() never called! when using shrinkwrapped dependencies

npm login errors

and it generally seems to work.

npm hangs on Windows at addRemoteTarball

Look for lines defining the tmp config variable. If you find more than one, remove all but one of them.

See https://github.com/npm/npm/issues/7590 for more about this unusual problem.

npm not running the latest version on a Windows machine

NPM: ENOENT: no such file or directory, rename

I was using gulp on the project, then i decide to deleted all the dev dependencies to switch to webpack, but every time i try to install using npm is get this error:

any idea what can be happening.

29 Answers 29

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

just delete package-lock.json file and then install packages, that’s all you need and should be works

When I got this error I looked for all running instances of node in my task manager (i use process explorer on windows) and close/kill all running instances of node. For me its often webstorm or vs code. After closing these programs and ensuring there is no running node process npm install works again.

cache verify command resolved the issue for me

Iam using
—node v15.5.0

example: npm i @react-navigation/native

This will fix the issue.

The second line may give a hint on what’s happening:

It looks like npm doesn’t have enough permission on the folder you’re trying to use.

ok change version of npm for the last version 5.8.0 now everything working just perfect, before was some kind of problem with atom that denied the permission the building process to install the dependencies of the package.

I just retried to run

and it succeeded

For me, package-lock.json was not created and script was failing before itself.

This fixed my issue:

If you ever get this error, the hotfix is to follow these steps:

Actually the current package you are installing has some dependencies which is not being found my npm. So, before installing this package just perform the following command. (It will install all your listed dependencies mentioned in package.json file which are necesaary to run your application)

For not to delete package-lock.json or node_modules every time, just add file «.npmrc» with content «package-lock=false», or add this string if file «.npmrc» already exists.

You can try by removing the package-lock.json with the command rm package-lock.json then you go to the Node.JS website you ‘install it’ by going to LTS then after your node is updated run npm install in your terminal and that worked for me.

Just update the node to the latest version. It solved my problem.

I was running command in Ubuntu wsl and it wasn’t working so i tried running in cmd prompt and it worked

Kindly check any package.json is open anywhere, then close it first then retry.

For me I just deleted both package-lock.json & node_modules folder. Now everything works great 😃

Another thing I’ve seen a lot on projects that have been around and gone through multiple contributors:

The tell-tale sign is you’ll see a package-lock.json (generated by npm) and yarn-lock.json (generated by yarn) in the same repo. This can cause side-effects from collisions in the node_modules folder.

You can try dumping that folder locally, establishing a package manager of choice for your project and instructing the whole team on best practices.

npm start errors with ERR! code ENOENT, syscall open

I’m suddently having a problem with «npm start» in my React application. When I trigger it, this is what I receive:

This is the debug.log:

I tried the following solution:

And then npm install returns:

My npm version is: 6.13.7

This is my package.json

ADo you have any ideas on the possible causes and the possible solutions?

23 Answers 23

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Just cd to the app directory where package.json is and run npm start again.

I think you forgot to open a terminal inside the project folder

so solution is change directory to your path where your package.json file is

My project folder is Currency not CurrancyConverter

This is because you have done

from outside the project directory to overcome this issue. first do

I hope this will solve your issue because it works for me.

Your stated error:

npm WARN saveError ENOENT: no such file or directory, open ‘/mnt/c/Users/pal/Desktop/dev/myApp/package.json’
npm WARN enoent ENOENT: no such file or directory, open ‘/mnt/c/Users/pal/Desktop/dev/myApp/package.json’
npm WARN myApp No description
npm WARN myApp No repository field.
npm WARN myApp No README data
npm WARN myApp No license field.

You can check the bold lines. It explains that you are not in the directory which contains the package.json file.

Most of the times you should run this command in the app directory. So, you need to cd into the directory which holds package.json then there you can run your commands like npm install, npm start etc.

So, before running these commands please check if you are in the correct directory.

npm install ERR! code ENOENT

1 Answer 1

Installing ionic when your running behind a proxy

Uninstall Node.js if your facing a lot of errors.(optional)

Install Nodejs(mandatory)

Install Python(mandatory)

During installation ensure that environmental variable for python is checked

Step 1: start->cmd->(right click ) run as administrator

Step 2: type the following command **cd** to work as a root user

Step 3: Setting up windows proxy as below(use your organisation proxies)

Step 4: Setting up npm proxy as below(use your organisation proxies)

Step 5: Dont navigate to the user folder(From the root folder) execute the following command

which will install both ionic and cordova.

Possible Errors:

NPM «ENOENT: no such file or directory error» when installing Sails.js dependencies with Node 8.9.4 LTS

I recently upgraded my computer and with it, to the latest LTS version of Node and NPM:

I have a Sails.js 0.12.14 application for which I’m trying to install NPM dependencies with npm install but when I do that, I get the following errors:

6 but after upgrading to Node 8.9.4 and NPM 5.6.0, it just won’t install my dependencies. How can I resolve this?

14 Answers 14

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Try deleting the package-lock.json file.

Or you can use no-optional flag.

It may be a problem with the cache, try to verify the cache.

Deleting and regenerating ‘package-lock.json’ usually solves this issue however that’s inherently risky because you will likely be upgrading multiple packages at a time.

In my case it turned out that there was one specific package version that package-lock.json was referencing, that was 5 levels deep in the dependency. That version no longer existed at the npm registry so it caused the install to break. I had to find which package was pulling in this dependency and upgrade that one to resolve the issue.

Just delete package-lock.json file and then install package(s) you want. All will work.

I was struggling with this for awhile, and it seems be be related to the following.

Let’s say you have 3 modules, A, B and C

Module A includes B and C directly Module B also includes module C, in it’s package.json dependencies.

If your package.json dependencies in module A look like the following:

If on the other hand you include the module with the nested include first like:

The error goes away. This seems like a bug in npm with nested dependencies, and the error messages and logs were not very descriptive. Check your dependency tree and see if you have the described case, if so, that is your issue.

How to fix: npm ERR! enoent ENOENT: no such file or directory, rename

Finally, I found a solution and a reason for that issue.

The error occurred when I was trying to install @testing-library/react npm package. It looked like that:

Hotfix

If you ever get this error, the hotfix is to follow these steps:

It should all work fine after that. But it’s only a hotfix, a solution for now to unblock you.

Coldfix (solution)

The reason for the issue is the jest tests runner working in the background. You can see that in the VS Code bottom bar:

The real solution is to disable jest runner when installing new packages. You can do it with a Jest: Stop Runner command in Ctrl+Shift+P:

In this second short post from SQLite-Net Extensions series, we’re going to see how to…

In the 3rd post from SQLite-Net Extensions series we are covering the last type of relationship…

In today’s post we’re going to see what is SQLite-Net Extensions ORM and how to…

docker-compose fails to start with npm ERR! enoent ENOENT: no such file or directory, open ‘/usr/src/app/package.json’

I built an image from a docker file to run node and copy in a simple node express app which works perfectly. The image builds I can run a container and bash in and the local files are copied. When I use this image in a docker-compose file along with a mongo image the containers build but the node container fails to run with an error is the package.json is missing.

The error returned is

Docker-compose.yml looks like

How has the package.json gone missing? Thanks for your help!

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

When your docker-compose.yml says

it hides everything that gets done in the Dockerfile and replaces it with the current directory. If your current directory doesn’t have the package.json file (maybe you moved everything Docker-related into a subdirectory) it will cause the error you see.

Personally I would just remove these two lines, develop my application locally (without Docker, using the per-project node_modules directory for isolation), and only build the Docker image when I’m actually ready to deploy it.

the /app name is this:

I also face same problem on Ubuntu 20.04 and docker-desktop 20.10.16 I changes following:

Before Solving Problem:

And docker-compose.yaml file contains:

After Solving Problem my files look like

I tried to run yo angular in a new project directory, but it gave me the ENOENT error somewhere along the way. Yes I have looked at this similar question, but its solution doesn’t work for me.

I ran these things on the empty new project directory right before running yo angular :

But I still get:

How can I fix it?

Here is the history of ALL the commands, in chronological order, that I ran on a brand new Ubuntu Server 12.04.3, so you can see exactly what led up to this point, and where I have installed various packages.

This question is linked to an npm github issue.

5 Answers 5

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had this same issue on Windows 7 machine. Here are the steps I took to resolve:

npm ERR! code ENOENT npm ERR! syscall open

I am trying to install npm in a laravel homestead folder but i get these error messeges. error messages in terminal

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I’ve suffered with this issue for a long time and it seems that the problem is using npm install as a vagrant user inside a laravel/homestead box so the main issue is one of permissions on a synced folder which is the main task of Homestead.yaml.

There’s two solutions for this problem:

One will enable you to work from homestead normally, and the other is just like a patch of sorts.

Insert the next line just below your folder mapping on Homestead.yaml

Next option is just working from your system, that has all permissions since it owns the folder in wich you are working.

Instead of executing npm install inside vagrant go to the folder in your system (your computer) and use the command from there.

If you need to clean install your project use:

app.js

package.json

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

delete nodemodules the run npm install

delete nodemodules the run npm install if now working delete package-lock.json

delete nodemodules and reinstall

Not the answer you’re looking for? Browse other questions tagged react-native or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Comments

dina06 commented Jan 3, 2020

npm ERR! A complete log of this run can be found in:
npm ERR! C:\tmp\nodejs\npm-cache_logs\2020-01-03T10_49_19_606Z-debug.log
Command npm.cmd failed with exit code 1

The text was updated successfully, but these errors were encountered:

dina06 commented Jan 3, 2020

halfnelson commented Feb 8, 2020

The latest version of this template no longer references halfnelson/svelte-hmr, I’d give it a go (check the history of the package.json file to see where I replaced it with the official version of svelte-hmr)

HamzaMansouri7 commented Apr 1, 2020

git-room-hub commented Aug 1, 2020

hollis-rp commented May 2, 2022

скачал GIT помогло!

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

npm install ERR! code ENOENT

1 Answer 1

Installing ionic when your running behind a proxy

Uninstall Node.js if your facing a lot of errors.(optional)

Install Nodejs(mandatory)

Install Python(mandatory)

During installation ensure that environmental variable for python is checked

Step 1: start->cmd->(right click ) run as administrator

Step 2: type the following command **cd** to work as a root user

Step 3: Setting up windows proxy as below(use your organisation proxies)

Step 4: Setting up npm proxy as below(use your organisation proxies)

Step 5: Dont navigate to the user folder(From the root folder) execute the following command

which will install both ionic and cordova.

Possible Errors:

npm ERR! code ENOENT npm ERR! syscall open

I am trying to install npm in a laravel homestead folder but i get these error messeges. error messages in terminal

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

There’s two solutions for this problem:

One will enable you to work from homestead normally, and the other is just like a patch of sorts.

Insert the next line just below your folder mapping on Homestead.yaml

Next option is just working from your system, that has all permissions since it owns the folder in wich you are working.

Instead of executing npm install inside vagrant go to the folder in your system (your computer) and use the command from there.

If you need to clean install your project use:

npm ERR! Error: spawn ENOENT

When i try to push my code to heroku am getting following error. Everything was working fine earlier. Suddenly something went wrong.

I have following packejer.json file

Please help me to solve this issue. Thank you.

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You can update the npm version in package.json since npm version you have given is out-dated.

will solve the problem.

You must have msysgit installed on your machine. Also, the path to my Git installation is «C:\Program Files (x86)\Git». Yours might be different. Please check where yours is before continuing.

enoent ENOENT: no such file or directory,

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is related to npm not being able to find a file. The error-message npm ERR! enoent is telling you that the file can’t be found.

First check if the file actually exists on your fs under that path and check the reference-path you use to call that file for possible typos.

If this is a fresh project you can call

and node will initliaize your project and create a package.json for you..

From the official docs:

Description: npm init can be used to set up a new or existing npm package.

The init command is transformed to a corresponding npx operation as follows:

For more detailed information please read the official docs about npm init.

npm ERR! enoent ENOENT: no such file or directory

I know this has been asked on her before but I’ve tried any solution I can find and still no luck. I downloaded a portfolio template which has been working fine with npm start until the past couple days I now receive this error:

I then tried to do git init but receive an error that I don’t have a start script in my json file. When I add the start script I receive this error:

This is my package.json:

Any help would be appreciated!

1 Answer 1

Furthermore, if this does not work, just try updating/reinstalling node. Maybe something with your npm installation is not properly configured.

Not the answer you’re looking for? Browse other questions tagged node.js npm or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

app.js

package.json

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

delete nodemodules the run npm install

delete nodemodules the run npm install if now working delete package-lock.json

delete nodemodules and reinstall

Not the answer you’re looking for? Browse other questions tagged react-native or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

ошибки установки npm с ошибкой: ENOENT, chmod

Я пытаюсь глобально установить модуль npm, который я только что опубликовал. Каждый раз, когда я пытаюсь установить, либо из npm или папки, я получаю эту ошибку.

Я использую sudo, и я трижды проверил все в пакете, все должно работать. Я сделал некоторые поиски вокруг, и увидел пару подобных случаев, ни один из которых не был решен. Вот что я попробовал.

Я заметил, что ошибка была связана с файлом, который я связываю с путем, особенно когда npm пытался сделать chmod. Это не должно быть проблемой, мой lib/cli.js имеет обычные разрешения, и npm имеет разрешения суперпользователя во время этой установки.

так в чем же дело? Это какой-то странная бахрома случай ошибка, что не имеет решения?

Edit: для справки,здесь это модуль, который я загрузил

24 ответов:

я столкнулся с подобной проблемой,

это удалило оба node и npm С моего пути. Оттуда я просто переустановил его

когда он закончил, у меня было node и npm на моем пути и я смог бежать

это затем успешно установлено bower.

Я попытался перейти в указанную папку, и она не существовала. Ошибка была исправлена, когда я созданоnpm на роуминг.

у меня была та же проблема, и просто нашел обработку, не упомянутую здесь. Хотя я бы внес свой вклад в сообщество:

Я получил аналогичное сообщение об ошибке при попытке npm install куча зависимостей. Оказывается, некоторые из них не удастся установить на Debian/Ubuntu, потому что они ожидают /usr/bin/node чтобы быть исполняемым узлом. Чтобы исправить, вам нужно сделать

Я получал аналогичную ошибку на npm install при локальной установке:

Я не уверен, что вызвало ошибку, но недавно я установил несколько новых модулей узлов локально, обновил узел с homebrew и запустил «npm update-g».

Я думаю, что ваш скомпилированный сценарий кофе отсутствует в опубликованном пакете npm. Попробуйте написать prepublish.

в моем случае (множественный код ENOENT errno 34) проблема была с

/.npm/ открыть каталог. Внутри него были некоторые подкаталоги, имеющего root:root права, которые вызывали проблемы, когда я запускал команды как обычный пользователь (без sudo ). Так я поменял владельца всех подпапок и файлов внутри

/.npm/ dir в моем локальном пользователе и группе. Это сделало трюк на моем Ubuntu (на Mac тоже должно работать).

тест:

выше действие вызвало некоторые зависимости устанавливаются внутри

решение:

постоянно проверять, если

/.npm/ содержит субдиры с правами собственности (и / или разрешениями), отличными от вашей учетной записи локального пользователя, особенно при установке или обновлении чего-либо с sodo (корень). Если это так, измените владельца внутри

/.npm/ для локального пользователя рекурсивно.

Я получил эту ошибку при попытке установить плагин grunt. я обнаружил, что у меня была устаревшая версия npm, и ошибка исчезла после обновления npm до последней версии

У меня есть аналогичная проблема конкретно : Эр! enoent ENOENT: нет такого файла или каталога, chmod ‘ node_modules / npm/node_modules / request/node_modules / http-signature/node_modules/sshpk / bin/sshpk-conv Я перепробовал все решения, но не повезло. Я использовал vagrant box, и проект был в общей папке. Проблемы, кажется, только там, когда я переместить проект в другую, не общую папку (с хозяином), вуаля! проблема решена. Только в случае, если другое лицо использует также бродячие

/.npm ), но ничего не работает. Что решило проблему, так это обновление узла (и npm) до последней версии. Попробовать это.

вы можете получить эту ошибку, если ваш узел.js также как-то поврежден. Я исправил эту ошибку, удалив/перезапустив / установив узел.js полностью и он исправил эту ошибку, наряду с тремя другими загадочными ошибками, которые выбрасываются.

следующие вещи не исправлена проблема:

Как Я Исправлена проблема:

у меня была аналогичная проблема с другой причина: yo node генератор добавил «files»: [«lib/»] мой package.json и cli.js находился за пределами lib/ каталог, он был пропущен при публикации в npm.

Я получаю сообщение об ошибке » ошибка: ENOENT, stat ‘C:\Users\userName\AppData\Roaming\npm’. Но такого каталога не было. Создал каталог, и установка npm начала работать

Я недавно обновился до узла 4.2.1 на машине Windows 7 x64. При запуске

я получил аналогичную ошибку:

думая, что это связано с путем AppData, я играл с

изменить префикс, кэш и tmp поля, но получил ту же ошибку с новыми путями:

все команды запускались от имени администратора, поэтому у меня были полные разрешения.

тогда я подумал, что есть некоторые проблемы с существующими файлами, поэтому я побежал:

но получил ту же ошибку. Тем не менее, все еще были некоторые временные файлы, лежащие вокруг. Ручное удаление всех временных данных с помощью cygwin окончательно исправило проблема для меня:

если у вас есть только Windows cmd, вы можете использовать что-то вроде

чтобы удалить все подкаталоги (хотя если у вас есть глубоко вложенные зависимости узлов, это заведомо проблематично)

Итак, возможно, есть некоторые проблемы с обновлением npm и наличием версий bower или других пакетов, висящих вокруг. В моем случае это казалось проблемой

при установке ionic я получил ниже ошибки

не было никакой папки под названием ansi по этому пути. Я создал его там, и он установлен правильно.

Если вы попытались «сделать установку» в каталоге проекта с этой ошибкой, вы можете попробовать:

затем вы можете попробовать, чтобы «установить»

Если у вас есть «npm ERR! enoent ENOENT: нет такого файла или каталога, chmod ‘. /джем-бэкэнд/папки node_modules/Яш-украсить и JS/ОГРН/УСБ-украсить.js'», то вы можете попробовать установить некоторые предыдущие версии js-украсить, больше комментариев: https://github.com/beautify-web/js-beautify/issues/1247

и запуск «make install». Кажется, это работает в случае, если у вас нет других зависимостей, которые требуют более высокой версии (1.7.0) в этом случае вы должны понизить этот пакет также в пакетах.формат JSON.

ни один из выше работал для меня. Но yarn install работала, потом npm i начал работать. Не уверен, что пряжа фиксируется, но быстрое и простое решение!

Error «enoent ENOENT: no such file or directory, open ‘/app/package.json'» docker referencing to external folder

I have my whole nodejs code in abc folder

I have created Dockerfile in following manner:

When i am running my docker container in following way,it gives error:

Contents of package.json file is as follows:

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I’ve modified your Dockerfile a bit, and it seems to work now here.

Try if it works and post back 😉

I had this exact error and it turned out to be an issue with docker-compose. For me I’m running WSL in windows and the version of docker-compose installed inside WSL was not handling volume binding correctly. I fixed this by uninstalling /usr/local/bin/docker-compose and instead aliasing the windows exe alias docker-compose=»/mnt/c/Program\ Files/Docker/Docker/resources/bin/docker-compose.exe»

I had the exact issue using docker-compose with Docker for Windows. Was able to resolve it by hitting «Reset credentials» and reapplying checkboxes for the needed drives.

Not the answer you’re looking for? Browse other questions tagged node.js docker or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

app.js

package.json

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

delete nodemodules the run npm install

delete nodemodules the run npm install if now working delete package-lock.json

delete nodemodules and reinstall

Not the answer you’re looking for? Browse other questions tagged react-native or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

npm WARN enoent ENOENT: no such file or directory, open ‘ /node_modules/supertest/package.json’ #261

Comments

joshua-barnett commented Feb 3, 2016

I installed supertest before installing debug and it fixed this error.

Maybe make it a dependency of this module?

The text was updated successfully, but these errors were encountered:

mooyoul commented Apr 8, 2016

No. That’s not an issue of debug package.
I think it’s related to NPM v3’s changed installation behavior.

You can resolve that issue by following methods:

if issue not resolved even tried these methods, Please reply with your Node.js version, NPM version, Operating System, and package.json which is using.

FaShapouri commented Sep 16, 2016

@mooyoul I have that problem and tried your solution. But my problem did not resolve.
I am using mac os 10.11.4 and Node 6.2.2 and npm 3.9.5

There is no package.json at ‘/Users/muser/package.json’

What is wrong in my setup? and how can I fix it.

mooyoul commented Sep 17, 2016

Okezie commented Dec 8, 2016

TooTallNate commented Dec 8, 2016

mriscoramdani commented Jan 8, 2017

Try to change your node.js version

osa9j commented Feb 2, 2017

dylannirvana commented Feb 13, 2017

Indeed what it wants is a package.json file, obtained by typing npm init. Then I was able to do an npm install with success.

anilkumarsoni commented Feb 15, 2017

mukun-bhatta commented Mar 8, 2017 •

shmooth commented Mar 9, 2017

i was operating in my main ‘dev’ directory:

/dev$ npm install

but i needed to be in my cloned git directory:

/dev/quiztool$ npm install

MarcioDuran commented Mar 14, 2017

$ npm install debug
npm ERR! Linux 4.8.0-22-generic
npm ERR! argv «/home/ubuntu/.nvm/versions/node/v7.7.2/bin/node» «/home/ubuntu/.nvm/versions/node/v7.7.2/bin/npm» «install» «debug»
npm ERR! node v7.7.2
npm ERR! npm v4.1.2
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo

npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network ‘proxy’ config is set properly. See: ‘npm help config’

npm ERR! Please include the following file with any support request:
npm ERR! /home/ubuntu/npm-debug.log

sudosoph commented Mar 22, 2017

If you don’t initialize your repo using npm init and complete package.json fields properly (or leave some blank), you might still get warnings. I followed this template and errors are gone: https://docs.npmjs.com/getting-started/using-a-package.json

WJLkalin commented Apr 5, 2017

amaljose01 commented Apr 7, 2017

the output you will get as below

jitendragupta2 commented May 23, 2017

while publishing my package was having package.json. so why it is not downloaded when i am installing my package

ctoxyz commented May 26, 2017 •

New to node. setup EC2 > AMAZON linux.. Node setup.. tried all kinds of versions..

no matter what i do, errors are obtained during install..

tried npm init. tried diff versions of all parts. still I can’t get a successful install & test code always fails.

Errors below. Please advise

npm install pdfkit
npm WARN saveError ENOENT: no such file or directory, open ‘/home/ec2-user/package.json’
npm WARN enoent ENOENT: no such file or directory, open ‘/home/ec2-user/package.json’
npm WARN ec2-user No description
npm WARN ec2-user No repository field.
npm WARN ec2-user No README data
npm WARN ec2-user No license field.
npm WARN ec2-user Invalid dependency: png-js undefined

No matter what I install or how, i get these:

Error while running the command npm install

I’m trying to run a react code and used the command npm install and error(s) pop up:

Help me resolve these errors, Thanks in advance!

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

The issue is that npm can’t find the package.json file.

Normally, this is a very simple problem that can be fixed easily.

1. Not in the directory of package.json

If you already have the package.json file, then you need to make sure that you are in the directory in which the file is in.

To see if the file is in your directory, run the dir command.

If you aren’t in the directory in which package.json is in, then navigate to that directory.

2. Creation of package.json

Another issue that can occur is that you haven’t yet created a package.json file.

To do this, run the following command.

However, if you don’t want to answer the questions from running that command, run the following.

This will initialise the package.json file in your directory.

That means that you have a dependency conflict. To fix this issue, run the command with the following flag.

This will resolve any incompatible packages (e.g. one package needs a lower version then what you currently have).

After you have done either of these solutions, then running the command below should work successfully.

I am trying to compile a Nativescript application as part of our Teamcity deployment strategy.

When I run NPM install, I get a ENOENT error trying to find files, as shown below:

I have tried cleaning up the node_modules folder,

I have also tried running the same steps in a local machine, with the same container, and the compilation is working.

There seems to be some dirty data related to npm or something similar causing this, but I can’t find out what.

This is the dockerfile being used:

How can I clean this up?

UPDATE

I have also noticed that npm uninstall loadash triggers the same behaviour and the multiple enoent messages.

Not quite sure why.

4 Answers 4

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Make sure that log output is the end of it.

In my case it was:

If not, check the end of your log for the actual issue. I experienced this when running a docker container and it turned out one of the packages is being pulled using git as you see in the log, so the git command needs to be in the PATH of the user that runs the npm command.

If it’s not that, the end of the log will likely tell you what is the actual error. If it’s not clear, it might be the package-lock.json file having old references generated by the package.json when running npm install. Try to remove/rename it and run npm install, then compare the differences.

If that still does not fix it, maybe package.json has a reference that is too old to be resolved by npm.

The npm cache you may be looking for on a Linux system is usually under

/.npm-global depending on how you configured npm/node.

If none of this resolves it, please update your answer with a full log, and the exact environment and conditions you run this in. If this only happens for lodash, try to see what happens if you remove it as a dependency. Good luck

enoent ENOENT: no such file or directory,

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is related to npm not being able to find a file. The error-message npm ERR! enoent is telling you that the file can’t be found.

First check if the file actually exists on your fs under that path and check the reference-path you use to call that file for possible typos.

If this is a fresh project you can call

and node will initliaize your project and create a package.json for you..

From the official docs:

Description: npm init can be used to set up a new or existing npm package.

The init command is transformed to a corresponding npx operation as follows:

For more detailed information please read the official docs about npm init.

«Couldn’t read dependencies» error with npm

I wanted to start a Node app and created a package.json file with a tutorial. Here is the json file:

I verified JSON file before trying to run it, but still I got an error message when I ran the npm install command:

and here is the npm-degub.log file

17 Answers 17

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had an «Invalid Name»

I switched from «name»: «Some Name». to «name»: «Some-Name».

Guess name needs to be a sluggy string.

Try to add this:

it worked for me.

EDIT (for people asking why):

The Oficial documentation states the following:

If you set «private»: true in your package.json, then npm will refuse to publish it. This is a way to prevent accidental publication of private repositories. If you would like to ensure that a given package is only ever published to a specific registry (for example, an internal registry), then use the publishConfig hash described below to override the registry config param at publish-time.

The error messages you are getting may be related to violating this «rule» in a way (mine was).

I tried to run yo angular in a new project directory, but it gave me the ENOENT error somewhere along the way. Yes I have looked at this similar question, but its solution doesn’t work for me.

I ran these things on the empty new project directory right before running yo angular :

But I still get:

How can I fix it?

This question is linked to an npm github issue.

5 Answers 5

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had this same issue on Windows 7 machine. Here are the steps I took to resolve:

Amazon Elastic Beanstalk npm cant find package.json

I’m very new with amazon web services, and I am trying to set up a node.js app on their elastic beanstalk. I set up the instance and uploaded/deployed the site, but while the health is «Ok» the node.js logs show this repeated about 30 times:

The problem is that my package.json does exist because I generated one with npm init. Any ideas on why it cant be found? Here is the package.json

5 Answers 5

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

From an official AWS thread[1], it appears (and this was my problem) that you might be zipping the top-level directory rather than zipping the source itself.

For example, you may have all of your files in a folder called «Project». Rather than zipping «Project», you should zip and upload the contents of «Project».

I fixed this setting in the port near top of my app.js or server.js file, just after I create the express app. For example:

Then using this port in the app.listen method instead of my own custom port number:

I was having these odd error on AWS EB as well. I was generally deploying using the CLI.

couple things to try.

i was using the t2.nano instance (512MB space) option for EC and that seemed to be an issue because I had a lot of modules in my package.json. Wasnt sure if that was the root issue of my woes but my error messages changed when I upgraded to an instance that had at least 1GB of space.

hope this helps

I had trouble with the zipping, etc. I recommend using CodePipeline and linking it to your github or AWS codecommit. Then, skip the build stage, and for the deploy stage click elastic beanstalk.

You will have to pause the process and open a new tab and go to EB and create a new environment. Make sure you click nodeJS in this example. Make sure you choose «sample code» so that AWS can set it up with their template. Once the EB is finished building you should have a link to the template that is functional.

Then you can go back to your CodePipeline tab and click on Elastic Beanstalk for deployment and you should find the EB you just made.

I recommend this process because it will automatically update every time you do a git change. This is better than zipping a file, etc.

npm ERR! Error: spawn ENOENT

When i try to push my code to heroku am getting following error. Everything was working fine earlier. Suddenly something went wrong.

I have following packejer.json file

Please help me to solve this issue. Thank you.

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You can update the npm version in package.json since npm version you have given is out-dated.

will solve the problem.

You must have msysgit installed on your machine. Also, the path to my Git installation is «C:\Program Files (x86)\Git». Yours might be different. Please check where yours is before continuing.

Cloud Functions deploy error during lint on Windows: «enoent ENOENT: no such file or directory»

Part of Google Cloud Collective

Following the firebase function getting started guide and getting a seemingly simple error once trying to deploy with:

The package.json file does exist just as the tutorial shows in my project/functions/package.json. Have tried changing or printing out the RESOURCE_DIR env with no success. Assuming it would be scoped inside of the NPM shell environment.

npm version: 5.6.0

node version: 8.9.0

10 Answers 10

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

The team is looking into ways to prevent having to make changes to the config files you use, as it’s not really convenient for teams that works across platform to keep changing the same file back and forth.

EDIT: This issue should be fixed with projects created with CLI version 3.17.5.

npm or yarn test fails with «npm ERR! enoent spawn bash ENOENT»

I am trying to follow a tutorial on how to fork Compound (https://medium.com/compound-finance/a-walkthrough-of-contributing-to-the-compound-protocol-9450cbe2133a). I want to add a new token. But in order to do that, I need to first be able to get the app to pass all tests.

The problem is that I can’t get the tests to run in the first place. According to the tutorial, I simply need to type yarn test to run the tests. However, when I try to do this, I get error messages that seem to imply that it cannot find the path to the test file. For example:

‘.\script\test’ is not recognized as an internal or external command, operable program or batch file. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.» >

After investigating some, I discovered that it is trying to run a script in package.json called «test».

The script looks like this: «test»: «./script/test»,

At first, I got a response saying that «.» is not a recognized command. I then tried to put the entire pathname in it so that it wouldn’t have a period in it. So I edited package.json to say «test»: «C:/Users/tombl/Documents/Code/compound-protocol/script/test»,

That didn’t work. Next, I tried to edit the environment variables in Windows so that CMD would recognize the folder (I’m using a terminal from within Visual Studio Code). That didn’t work either.

In addition, I tried editing package.json so that there is a second set of quotes in the path, like this: «test»: «‘C:/Users/tombl/Documents/Code/compound-protocol/script/test'», But it still didn’t work.

At this point, I have no idea what to try next.

I can see very clearly in file manager that the «test» file is there and that the path I’ve stated is correct. I can even open up the test file and see the code inside of it. But I can’t get the terminal to run it. It just says that it isn’t there.

One clue I do have is that it stops at the folder «compound-protocol». So it either doesn’t recognize the folder compound-protocol at all or it doesn’t recognize that the script folder is inside of it.

I’ve wondered if maybe the hyphen in «compound-protocol» is causing the problem, but the only advice I’ve gotten on how to fix that is to put the whole path in quotes, which I’ve already tried.

I’ve even tried navigating to the script folder within the terminal and running the test from there. While it does let me navigate into the script folder, trying to run the test produces a > Program ‘test’ failed to run: No application is associated with the specified file for this operationAt line:1 char:1. > error message.

Does anyone know how I might go about fixing this?

npm ERR! code ENOLOCAL

after making a software to my laptop I installed all the programs includes node js my OS windows

when I tried to install npm globally it’s gave me this error :

or even when I tried to install it locally to a repository it’s gave me:

any help would be appreciated

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had same problem. I solved in this way.

Step 2: run npx create-react-app your-app-name

I got the same issue. What I did was to rename the package-lock.json by:

, and then this issue should be solved.

These steps works for me. Hope they could be helpful to you too.

[BUG] npm install followed by npm ci fails with no such file or directory (chmod failure) #2251

Comments

tmanning commented Nov 27, 2020 •

When you run npm i successfully followed by npm ci the operation fails.

When you run npm i successfully followed by npm ci it should complete without errors.

Steps to reproduce

npm i generates a package-lock.json
follow this with
npm ci
and it fails looking for node_modules/aws-cdk/bin/cdk

npm 6 does not exhibit this problem.

Environment:

The same occurs on linux

The text was updated successfully, but these errors were encountered:

darcyclarke commented Jan 29, 2021

troyready commented Jan 29, 2021

Issue persists from what I can tell:

Results in the following:

Log file contains:

jayphelps commented Feb 2, 2021 •

Hitting this as well only using GitHub Actions + npm v7 but not locally on any devs machine. Happy to provide any info to help debug or Zoom. (npm@7.5.2). Mine isn’t with aws bin but instead @cloudflare/wrangler’s bin.

I tried doing some digging but I’m unfamiliar with the codebase. It seems like maybe the linking of bins is ultimately handled by another library npm folks maintain bin-links. Didn’t see anything immediately screwy, but then again it seems to handle lots of edge cases, and the problem might be higher in the code.

fluiddot commented Feb 9, 2021 •

After following these steps and even in a clean install I don’t get the error again. However this is just a workaround, I wouldn’t expect to have to install dependencies with a previous version.

My impression is that having the following combo produces the issue:

I’ve got the following Dockerfile for a React app and I’m running tests after I build this container. This is my first day with Docker and I’m following a course, so not really sure what I’m doing.

Since I added the two RUN statements (which I’m not sure is a good idea) the build is still successful, but then I run the tests with docker run ID npm run test and I get the following error:

My file structure is this:

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is an multi-stage build.

To solve this problem you could do the following

The overall multi-stage build pattern you show here is typical for producing a deployable image with a browser-based application compiled down to static files. The entire contents of the image are the last stage, starting from the final FROM line:

There’s no rule that you must use exclusively Docker-based tools, even if you’re eventually shipping a Docker image. For day-to-day development I’d recommend using a host-based Node environment, rather than trying to indirectly use Docker to simulate it. Then you can run your unit tests before you package up your application.

Since I added the two RUN statements (which I’m not sure is a good idea) the build is still successful, but then I run the tests with docker run ID npm run test and I get the following error:

My file structure is this:

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is an multi-stage build.

To solve this problem you could do the following

Problem with npm start (error : spawn cmd ENOENT)

I have a problem with my application. Because before when I created an application it worked, but now, it shows me this error and I do not know why and the things I have to do to fix it.

I checked some stackoverflow topics but everywhere I checked, it was not really an answer that worked.

5 Answers 5

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Add C:\Windows\System32 to the global PATH environment variable.

Solution 1

Solution 2

If the first one doesn’t work follow the 2nd steps. Navigate to your project folder and type this command >>>

Solution 3

Downgrade react-scripts in package.json file

I had the same problem after I tried to install Mongo DB. I found out that this problem only exists with react-scripts@3.0.0. Try to reinstall your npm with a different react script version. Simply go to your folder in command and reinstall like this:

After that the app worked for me again.

For all those Who’ve come to this problem from react scripts not starting. The solution is

Not the answer you’re looking for? Browse other questions tagged node.js reactjs windows git-bash or ask your own question.

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

npm ERR! code ENOENT, npm ERR! errno 34

This is my start script for a React application.

When I run npm start, I get a long list of error.

So clearly the npm script is failing because it’s trying to look for the wrong path. npm ERR! path /home/user/workspace/shareback-viewer/node_modules/lint/package.json

How can I fix this?

1 Answer 1

Whenever I had this error deleting the node_modules and running npm install in again seems to do the trick, npm start kicks of after that little work-around. I’ve seem a ton of issues on GitHub about this and most people suggest using the above suggested method. If you see other npm errors you can check the official docs for error troubleshooting. If it still occurs try npm cache clean command, note that you may need to add the —force flag sometimes. Hope this helps!

Not the answer you’re looking for? Browse other questions tagged node.js npm or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

I tried to run yo angular in a new project directory, but it gave me the ENOENT error somewhere along the way. Yes I have looked at this similar question, but its solution doesn’t work for me.

I ran these things on the empty new project directory right before running yo angular :

But I still get:

How can I fix it?

This question is linked to an npm github issue.

5 Answers 5

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I had this same issue on Windows 7 machine. Here are the steps I took to resolve:

npm ERR! code ENOENT when adding cordova plugins (cordova deletes the file it’s looking for)

I am trapped in a somewhat infinite loop of struggles! Please help xD

No matter what phonegap or cordova cli commands I run, cordova seems to delete the very files it’s looking for previous to looking for them.

Here are just a few known commands which trigger the error for me:

$ cordova plugin add

$ phonegap plugin add

$ cordova platform update

$ phonegap platform update

$ cordova platform remove

$ phonegap platform remove

See below terminal output which shows the output I get when running these commands. I am really unsure why cordova is deleting the very file it’s trying to rename before it tries to rename it. Very frustrating!

Step 1 (check to ensure we have a clean git head and no changes in our working set)

Step 2 (attempt plugin add)

Step 3 (check git changes caused by the command in step 2)

Okay, so it failed. Let’s find out what happened to the supposed missing file. Well, apparently cordova deleted the file before it looked for it?

If anyone has any suggestions on how to fix this issue, I’d be super grateful. I’m not sure what caused it or when it took effect, but it’s been a couple weeks now that I haven’t been able to add plugins to my project.

Thanks in advance!

EDIT: Environment settings:

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I really don’t know where is a problem in your project but I had similar behavior when I upgraded cordova version and migrated my project from Eclipse to Android Studio.

Adding some plugin causes to multiple deletions and all my project doesn’t work.

I tried a lot of ways to fix it but failed, every time with other Exceptions.

So I solved it by creating new project from scratch. Added all plugins one by one and after, copied all www folder from old project.

It took me about 30 min but it worth it.

Hrmm, so I was able to fix this issue. The discussion in the thread was helpful in leading me to the correct answer without actually solving it.

Here’s what I did:

Step one: Update cordova

Phonegap was already updated to the latest version but my cordova wasn’t.

Step two: Update node and npm

Apparently, after updating these 2 components everything in my app played nice again. At this point it would install into /plugins using phonegap plugin add

but it wasn’t propagating the plugin code to Android until I switched the location of the Maven repository.

Step three: Update Maven repository location in build.gradle

It’s not really related to my question but I was able to build the apk permissions as soon as I changed the Maven repository location in /phonegap/platforms/android/build.gradle

Here’s what I changed in build.gradle.

My original build.gradle settings:

Which I changed to:

After that I was able to build my APK with the correct plugin permissions and use the plugin I added.

I keep getting `errno 4058` from npm

I used npm in the last weeks without any problems, but all of the sudden i keep getting this error:

This is the package.json :

The thing is, it also happens when I manually install a package. What am I doing wrong? Thanks

Edit: And when I tried it on a different directory the manual installation worked. I have no idea why.

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

There are no other Node processes running. I closed Visual Studio Code, still seeing ENOENT.

QuickFix: Delete package-lock.json and run NPM again

try this to solve your error

1st check your port is running or not through this command

I’m trying to run npm install for a little ember-driven site that I’ve got, but it throws the following error:

If I delete the node_modules directory completely then run npm install again it seems to work, but running it again fails.

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

What you can try is:

Be sure that you use cmd promt in Admin mode.

If you use VS Code, kill all node procceses. Close it and try again.

One of it can help. But not for sure. The status of issue with this problem is open for the moment. https://github.com/npm/npm/issues/17444

I just had this issue when setting up a new machine. None of the cache clean/uninstall/reinstall steps worked for me.

However, I was able to resolve it by updating npm to the latest version. I had 5.6.0 installed, but using npm-windows-upgrade to install the latest version (5.7.1) cleared up the dependency issues.

See this answer for more information on upgrading npm on Windows: https://stackoverflow.com/a/31520672/91189

This most likely happened because you updated your node version and because you probably already had this repo sitting on your machine before that particular update, the package-lock.json file whose sole purpose is to track the present and past state of your node_modules file and maintain a very updated dependency tree such that amongst entities using your code there will be consistency installing exactly the same dependencies ;

Entities using your code include

Deployments (AWS ECS),

and Continuous integration tools like Travis CI that are running your code,

Try to delete the package-lock.json file. Run the npm install command and you should be fine.

The last thing you should try doing is deleting the missing package if you are not sure of what you are doing, it’s usually better to avoid this.

NPM ENOENT errors when running Npm install

I’ve been trying to make a RoVer-based bot for my Discord server, but I keep getting ENOENT errors whenever I run npm Install.

I know there are other posts like this, but none of the answers have worked, and they aren’t exactly the same problem that I’m having. I’ve already tried reinstalling Node.js and NPM, making sure the package.json is there, restarting, and running as administrator. I am currently running Windows 10 version 1903, Node version 12.13.0, npm version 6.12.0.

Here’s the output:

4 Answers 4

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You have this error near the bottom of your log:

This means you do not have git installed on your machine. You need to install git from here: https://git-scm.com/downloads.

I had the same problem as you, and once I installed git, the problem went away.

Sounds a bit like it could be a permissions issue. Are you in the root of your project?