npm: ENOENT: no such file or directory

[matthewb...@gmail.com]

Hi all,

Just installing another instance of 2.9. And While I usually get the following error, I thought I would post it up for the crew to tell me if this is normal?

I have issues creating custom themes and maybe this is the root cause?

It happens when I do npm install while compiling the bootstrap 5 themes.

Is anyone else getting this?

If not, maybe the developers can chime in?

sudo npm install
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/user/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/user/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2025-07-02T09_40_50_656Z-debug-0.log

[matthewb...@gmail.com]

I suppose I should also ask, that if I hope to be able to change themes, should I install the developer files from the beginning? any known issues when I do it later?

[Hans-Arno Mielsch]

If you want to check, if it is caused by your custom theme, just delete the custom theme folder in atom/plugins and retry.

Reading the log, it seems as if /home/user is your AtoM-folder!?

That differs much from the installation guide where /usr/share/nginx/atom is proposed.

And changing the theme should primarily mean "create a new custom theme" - it is separated as aPlugin and based on the DominionB5ThemePlugin and far better to debug.

And no, you do not need to install developer files from the beginning.

Do a normal installation, test the success and then create your custom plugin from the documented template.

Regards,

-Hans-Arno

[matthewb...@gmail.com]

Ok thanks. That seemed to work this time. I had to download the package.json file manually cos it doesnt come with the the github way of installing it, which is what I was doing. As well as the other files.