HashLips / hashlips_art_engine

HashLips Art Engine is a tool used to create multiple different instances of artworks based on provided layers.
MIT License
7.18k stars 4.3k forks source link

HELP PLEASE ---npm ERR! code ENOENT npm ERR! #313

Open alessvuitton opened 2 years ago

alessvuitton commented 2 years ago

npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\Users\aless\Desktop\hashlips_art_engine-1.0.6_update/package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\aless\Desktop\hashlips_art_engine-1.0.6_update\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent AM GETTING THIS ERRO MESSAGE every time i type npm install.

magnius-ops commented 2 years ago

I am too I've tried re downloading everything and nothing seems to be working.

alessvuitton commented 2 years ago

found the problem bro.
you have to select the folders inside the folder.

join hashlips discord, theres a guy that knows how to fix it, he told me and he was right.

whe u select open folder, click and select the folder inside

magnius-ops commented 2 years ago

Thank you that works! Was trying to figure this out for so long bro thanks.

alessvuitton commented 2 years ago

bro, i was going crazy since last night lol. good luck

FunkySea commented 2 years ago

bruh this driving nuts lol.. open the folder in the folder I get this error. if I just open it up I get this

npm ERR! node-pre-gyp ERR! stack at ChildProcess.emit (node:events:390:28) npm ERR! node-pre-gyp ERR! stack at maybeClose (node:internal/child_process:1062:16) npm ERR! node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) npm ERR! node-pre-gyp ERR! System Darwin 21.1.0 npm ERR! node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/richardrodriguez/Desktop/hashlips_art_engine-main/hashlips_art_engine/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" npm ERR! node-pre-gyp ERR! cwd /Users/richardrodriguez/Desktop/hashlips_art_engine-main/hashlips_art_engine/node_modules/canvas npm ERR! node-pre-gyp ERR! node -v v17.2.0 npm ERR! node-pre-gyp ERR! node-pre-gyp -v v1.0.6 npm ERR! node-pre-gyp ERR! not ok

FunkySea commented 2 years ago

so can anyone help me

dasdot91 commented 2 years ago

found the problem bro.
you have to select the folders inside the folder.

join hashlips discord, theres a guy that knows how to fix it, he told me and he was right.

whe u select open folder, click and select the folder inside

What you mean by select folder inside. Can u explain😢😢

kaikecloss commented 2 years ago

Waiting for the soltion too

found the problem bro. you have to select the folders inside the folder. join hashlips discord, theres a guy that knows how to fix it, he told me and he was right. whe u select open folder, click and select the folder inside

What you mean by select folder inside. Can u explain😢😢

bolshoytoster commented 2 years ago

@FunkySea run ls -Directory in your powershell to get the name, then run cd + the name and you should be in the correct folder.

FunkySea commented 2 years ago

I tried that many times and I still got npm error

Sent from Yahoo Mail for iPhone

On Saturday, January 8, 2022, 6:02 AM, dasdot91 @.***> wrote:

found the problem bro. you have to select the folders inside the folder.

join hashlips discord, theres a guy that knows how to fix it, he told me and he was right.

whe u select open folder, click and select the folder inside

What you mean by select folder inside. Can u explain 😢 😢

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: @.***>

bolshoytoster commented 2 years ago

@FunkySea can you please paste the output of Get-ChildItem.

Ak143Mk commented 10 months ago

Screenshot_2023-12-02-13-36-41-62_84d3000e3f4017145260f7618db1d683

bolshoytoster commented 10 months ago

@Ak143Mk you've likely made this comment in the wrong place. You could try opening one on the ngrok-javascript repo, since it looks like that's what failed.