HashLips/hashlips_art_engine

Fix for Apple M1 Chips (makes your Hashlips Art Engine working)

deemount opened this issue · 109 comments

  1. Download the source and put it somewhere
  2. Be sure using a nodejs version around v14.17.3. Manage your version with nvm, if you need to!
    a) nvm install v14.17.3
    b) nvm alias default v14.17.3
    Be sure, you have no node version in your export path in zshrc
  3. Canvas 2.8 failed to install (main reason why it's not working on m1)? Put in your zsh or bash:
    arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg
  4. go now in the hashlips_art_engine root-folder and put in your terminal:
    a) npm install
    b) node index.js

Et Voila. Enjoy generating ...

9dieg commented

I tryed everything here, but still not working. I get this dlopen(/Users/*****/Desktop/hashlips_art_engine-main/node_modules/canvas/build/Release/canvas.node, 0x0001): symbol not found in flat namespace '_cairo_fill'

azf20 commented

@9dieg I think you may need to make sure your Homebrew is updated for your M1

9dieg commented

@azf20 didn't work..:s

it worked for me thaNK YOU

YOU MIGHT HAVE SOMETHING OR ANOTHER VERSION OF NODE ISNTALLED

I am only able to generate 2 images even though it's set to generate 10

@CobraKaiX does it give an error?

It worked Like a few times and now its not working again , it worked when I was testing it and now it doesnt work what did you end up doing

I am only able to generate 2 images even though it's set to generate 10

check on the OUTput next to terminal it sometimes gives you some feedback there

@funkymonkey5150 can you paste the error you get please.

same issue on my end only able to generate max 5 images and sometimes less

receive this error
TypeError: Cannot read properties of undefined (reading 'path')
at /Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:181:61
at new Promise ()
at loadLayerImg (/Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:180:10)
at /Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:361:31
at Array.forEach ()
at startCreating (/Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:360:17)
at processTicksAndRejections (node:internal/process/task_queues:96:5)

any ideas?

I found that installing the "Latest Features" version of node.js (17.8.0 as of the time of this post) and then installing the dependencies via Homebrew as indicated above worked perfectly.
arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg

Sounds good, I will test it, too. Thank you

It seems good for me, thanks @deemount

It worked! Thank you very much.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! hashlips_art_engine@1.1.1 generate: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the hashlips_art_engine@1.1.1 generate script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found

have this problem help please..

This doesn't appear to be related to Apple M1 Chips, based on the error. If you have a separate issue, please open a new Issue ticket.

@deemount have you confirmed that upgrading nodejs is successful for you? Ideally we don't want to be telling people to downgrade, for obvious reasons :)

@nfthorsy can you paste the full error please.

Had not the time, but would do it tomorrow and give you the information then

Reply from @ipv6freely:

@deemount have you confirmed that upgrading nodejs is successful for you? Ideally we don't want to be telling people to downgrade, for obvious reasons :)

I can confirm this one on my M1 machine. I had v16 previously and installed the v17 package to test it out.

steps:

  1. installed v17
  2. ran this command with homebrew arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg
  3. reopened terminal and vscode

notes:

  1. you may use nvm to install v17
  2. you may need to install homebrew if not yet in system

@deemount I'm trying to get my M1 Max running the art engine and no dice. Can you create a video that shows us how to follow the steps at the beginning of the thread? Think of it as nobody knows anything about this process since I'm a complete neophyte. Thanks! -D

@deemount I'm trying to get my M1 Max running the art engine and no dice. Can you create a video that shows us how to follow the steps at the beginning of the thread? Think of it as nobody knows anything about this process since I'm a complete neophyte. Thanks! -D

You don’t want to follow the steps at the beginning of the thread. You want to follow what I did and what @arjayosma confirmed works.

Install nodejs latest (v17) and then run the brew install command assuming you have homebrew installed. If you don’t have homebrew installed then download and install that (google it).

DUDE! Worked! Thanks a million-I was banging my head on my desk getting error after error. Thank you!

DUDE! Worked! Thanks a million-I was banging my head on my desk getting error after error. Thank you!

No problem!

I have an M1 Mac...trying to download homebrew and I keep getting a message about checking for sudo access...what am I doing wrong?

I have an M1 Mac...trying to download homebrew and I keep getting a message about checking for sudo access...what am I doing wrong?

You need to use sudo.

@ipv6freely - I am about as new as it gets....is that something I need to download?

@ipv6freely - I am about as new as it gets....is that something I need to download?

No, you just need admin privileges to install software. Do “sudo ” and put in your password to elevate privileges.

This is nothing to do with the software or homebrew, it’s a basic system command.

@ipv6freely - You're a saint. Thank you

@ipv6freely so I went through the process the tried to check the version with brew -v.... got a message zsh:command not found

@ipv6freely so I went through the process the tried to check the version with brew -v.... got a message zsh:command not found

Then homebrew is not installed correctly. You may need to seek out help with them… this is very off topic for this Issue ticket at this point and this isn’t really meant to be a place for discussion.

Thanks for the help

Installed homebrew and after I execute
arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg
I get following error:
arch: Can't find brew in PATH

What am I doing wrong?

@boehmatron you don't have homebrew installed or it's not installed properly.

This is probably the only time you can trust a command with both curl and /bin/bash -c. Run this to install homebrew:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

@bolshoytoster doesnt still work. do i need to execute
arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg
in a specific directory or do i need to prepare something beforehand?

@boehmatron try running arch -arm64 /opt/homebrew/bin/brew install pkg-config cairo pango jpeg giflib librsvg, if that works you can run echo 'eval $(/opt/homebrew/bin/brew shellenv)' >> /Users/$USER/.zprofile so you can just run brew instead of /opt/homebrew/bin/brew in the future (after restarting your terminal).

same issue on my end only able to generate max 5 images and sometimes less

receive this error TypeError: Cannot read properties of undefined (reading 'path') at /Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:181:61 at new Promise () at loadLayerImg (/Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:180:10) at /Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:361:31 at Array.forEach () at startCreating (/Users/saxonheller/Desktop/minter-dapp-main/backend/src/main.js:360:17) at processTicksAndRejections (node:internal/process/task_queues:96:5)

any ideas?

@saxonheller I'm having the same issue. Is anyone able to find a fix for this?

@RadZ3000 could you try using my fork.

@RadZ3000 could you try using my fork.

Thanks @bolshoytoster I just tried it and it does work, however the repo I'm working with is this one.

Can you tell me if I can replace the backend folder with your fork? I'm new to coding so not 100% sure.

@RadZ3000 you might be able to replace the backend/src/main.js with my src/main.js but I'm not too sure.

ps: in future you should probably ask questions in the place you got the code from.

@RadZ3000 you might be able to replace the backend/src/main.js with my src/main.js but I'm not too sure.

ps: in future you should probably ask questions in the place you got the code from.

It worked! Thanks man, been struggling with this for a while.

And yeah you're right. I'm here because I was directed to this fix by the code author, so I assumed it was the same issue.

@deemount it may make sense to close this Issue at this point. Most of the comments are completely off topic and have pretty much made the actual solution (#812 (comment)) impossible to locate. The original post of the Issue isn’t even correct anymore anyway and it’s likely to confuse people.

XQ99 commented

@deemount it may make sense to close this Issue at this point. Most of the comments are completely off topic and have pretty much made the actual solution (#812 (comment)) impossible to locate. The original post of the Issue isn’t even correct anymore anyway and it’s likely to confuse people.

This worked for me:

  1. installed home brew
  2. ran arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg in homebrew - took a while to dl all
  3. installed node via homebrew
  4. loaded vs, ran npm install within terminal

Who might be able to tell me if the is the same problem.

I have this error:

erikbos@Eriks-Mac-mini 13.ART-Engie % npm run generate
npm ERR! Missing script: "generate"
npm ERR! 
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

npm ERR! A complete log of this run can be found in:
npm ERR!     /Volumes/T5-500GB/Users/erikbos/.npm/_logs/2022-04-17T17_43_03_271Z-debug-0.log
erikbos@Eriks-Mac-mini 13.ART-Engie % 

After some Googling found this tread and this is what I have done:

  1. Install homebrew running this command
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)

  2. After install HomeBrew aske to run 2 additional commands
    echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> /Volumes/T5-500GB/Users/erikbos/.zprofile
    And
    eval "$(/opt/homebrew/bin/brew shellenv)"

  3. Than I run the command
    arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg
    A long installation process starts

Here I thought the AppleM1 problem was fixed and I could try to run the original command again
npm run generate

The same error appears. The one I used starting this question. So my question. Do i have the M1 problem or do I have a different problem and should look not in this tread but in a different one?

To be clear, there is no “M1 Problem”. Anyway, I’m not seeing where you upgraded nodejs to 17.x.

To be clear, there is no “M1 Problem”. Anyway, I’m not seeing where you upgraded nodejs to 17.x.

Check: there is no “M1 Problem”. Poorly expressed myself. I did not upgrade was already running that version got the latest version from their website.

Right on, there ya go. Need to get “latest” 17.x, not “stable”.

@LazySlothArt the error is because you're in the wrong directory. I trust you can use ls/cd to get into the main dir, the ls output shold look something like this in the right spot:

banner.png        index.js  logo.png      package-lock.json  utils
COMMON_ISSUES.md  layers    modules       README.md          yarn.lock
constants         LICENSE   package.json  src

Solved that was it thanks

i am getting this error when running "npm run generate"

(node:30542) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
(Use node --trace-deprecation ... to show where the warning was created)
node:fs:1413
handleErrorFromBinding(ctx);

i am getting this error when running "npm run generate"

(node:30542) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead (Use node --trace-deprecation ... to show where the warning was created) node:fs:1413 handleErrorFromBinding(ctx);

Nothing to do with the M1. I’d suggest asking for help in the discord.

ok Thanks

Thanks for this man!

I just want to add on, for people like me who had latest nodejs installed, I run the following commands:
npm install -g n
n 14.17.3

Then reopen terminal to check that the version indeed downgraded (node -v)

I had issue with the canvas code too, so I uninstalled and uninstalled.
npm uninstall canvas
npm i canvas

The rest just follow what this guy mentioned and it works perfectly! Good luck!

Thanks for this man!

I just want to add on, for people like me who had latest nodejs installed, I run the following commands: npm install -g n n 14.17.3

Then reopen terminal to check that the version indeed downgraded (node -v)

I had issue with the canvas code too, so I uninstalled and uninstalled. npm uninstall canvas npm i canvas

The rest just follow what this guy mentioned and it works perfectly! Good luck!

Downgrading is actually not the correct way to do it. This post is out of date.

The UPDATED method for ensuring your Node.js is the correct version for Apple M1 chips can be found here: #1115

@HashLips @deemount please go ahead and close this issue so people aren't confused.

Hi All - great thread and it's gotten me to where the art engine will run but fail after about 2/3 of any generate build. I happens with all of the builds over 500 but I've gotten complete builds around 300. I'm not a real coder so I apologize if this an easy fix.

This last build got to around 6786 of 9999 and gave me this error.


Created edition: 6786, with DNA: 8dbdec66c7a4e7b98f852852cbc472f16424d96d
(node:53185) UnhandledPromiseRejectionWarning: Error: error while reading from input stream
at Image. ()
at setSource (/Users/drn/Desktop/PIXEL PEW VSC V5/node_modules/canvas/lib/image.js:91:13)
at Image.set (/Users/drn/Desktop/PIXEL PEW VSC V5/node_modules/canvas/lib/image.js:62:9)
at /Users/drn/Desktop/PIXEL PEW VSC V5/node_modules/canvas/index.js:34:15
at new Promise ()
at loadImage (/Users/drn/Desktop/PIXEL PEW VSC V5/node_modules/canvas/index.js:23:10)
at /Users/drn/Desktop/PIXEL PEW VSC V5/src/main.js:185:27
at new Promise ()
at loadLayerImg (/Users/drn/Desktop/PIXEL PEW VSC V5/src/main.js:184:12)
at /Users/drn/Desktop/PIXEL PEW VSC V5/src/main.js:368:31
(Use node --trace-warnings ... to show where the warning was created)
(node:53185) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:53185) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


I tried the fix in the thread and got this error. I'm not a real coder so I apologize if this an easy fix.


drn@DRNs-MacBook-Pro PIXEL PEW VSC V5 % npm install -g n
/Users/drn/.nvm/versions/node/v14.18.2/bin/n -> /Users/drn/.nvm/versions/node/v14.18.2/lib/node_modules/n/bin/n

  • n@8.2.0
    updated 1 package in 0.137s
    drn@DRNs-MacBook-Pro PIXEL PEW VSC V5 % n 14.17.3
    installing : node-v14.17.3
    mkdir : /usr/local/n/versions/node/14.17.3
    mkdir: /usr/local/n: Permission denied

    Error: sudo required (or change ownership, or define N_PREFIX)

drn@DRNs-MacBook-Pro PIXEL PEW VSC V5 %


I'll try the #115 and see if that fixes it.

I also got this error when I ran "npm run rarity"


drn@DRNs-MBP PIXEL PEW VSC V5 % npm run rarity

hashlips_art_engine@1.1.1 rarity /Users/drn/Desktop/PIXEL PEW VSC V5
node utils/rarity.js

internal/fs/utils.js:332
throw err;
^

Error: ENOENT: no such file or directory, open '/Users/drn/Desktop/PIXEL PEW VSC V5/build/json/_metadata.json'
at Object.openSync (fs.js:497:3)
at Object.readFileSync (fs.js:393:35)
at Object. (/Users/drn/Desktop/PIXEL PEW VSC V5/utils/rarity.js:10:18)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47 {
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/Users/drn/Desktop/PIXEL PEW VSC V5/build/json/_metadata.json'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! hashlips_art_engine@1.1.1 rarity: node utils/rarity.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the hashlips_art_engine@1.1.1 rarity script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/drn/.npm/_logs/2022-04-23T23_54_27_280Z-debug.log
drn@DRNs-MBP PIXEL PEW VSC V5 %
drn@DRNs-MBP PIXEL PEW VSC V5 %
___________________________________________________________________-

Thanks homies!

D

@drn999 the first error says error while reading from input stream which is probably not to do with arm.

If you use my fork you can see what file/directory caused that error.

Hey - thanks for the reply. I'm not a savvy coder. What are the steps to fix this? I don't know what to change within the HashLips folder. Let me know if you can share the steps. -D

@drn999 just download the code from my repo, copy your src/config.js and layers/ over, npm install again then run it like you do the main repo.

I found that installing the "Latest Features" version of node.js (17.8.0 as of the time of this post) and then installing the dependencies via Homebrew as indicated above worked perfectly. arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg

yes, it works! thanks mate~

@.*** generate
/Users/cobrakaix/Downloads/hashlips_art_engine-1.1.2_patch_v6
node index.js
(node:15269) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'edition' of undefined at /Users/cobrakaix/Downloads/hashlips_art_engine-1.1.2_patch_v6/src/main.js:313:65 at Array.find () at saveMetaDataSingleFile (/Users/cobrakaix/Downloads/hashlips_art_engine-1.1.2_patch_v6/src/main.js:313:31) at /Users/cobrakaix/Downloads/hashlips_art_engine-1.1.2_patch_v6/src/main.js:408:11 at async startCreating (/Users/cobrakaix/Downloads/hashlips_art_engine-1.1.2_patch_v6/src/main.js:373:9) (Use node --trace-warnings ... to show where the warning was created) (node:15269) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:15269) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. I keep getting this error when I try to generate my images, this is an older version for reference.

On Tue, 22 Mar 2022 at 13:40, bolshoytoster @.> wrote: @CobraKaiX https://github.com/CobraKaiX does it give an error? — Reply to this email directly, view it on GitHub <#812 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX5PI5YHEP7FHQ4IV2IQBQTVBIV3JANCNFSM5PMRVF4Q . You are receiving this because you were mentioned.Message ID: @.>

Trying to figure how how this is different from what you posted yesterday. Did you mean to post an update?

This method is no longer the recommended way. Check #1115

Is there still a way to do it on this version? My images got corrupted and now they're only on this code file.

Honestly not sure what you’re asking. On what version?

@CobraKaiX I can't remember what the fix was, as several things can cause that error. I just know my fork fixed them.

My fork is compatible with this version so you can just copy over your layers/ folder and src/config.js.

@CobraKaiX I can't remember what the fix was, as several things can cause that error. I just know my fork fixed them.

My fork is compatible with this version so you can just copy over your layers/ folder and src/config.js.

Have you submitted a PR to have your changed merged? That seems like a much easier way to handle it versus pointing people towards a 3rd party fork.

@CobraKaiX you can get the zip, extract it, then copy over your layers/ folder and src/config.js.

@ipv6freely I've had a PR open for months, Hashlips is too busy to properly review it.

@CobraKaiX you can get the zip, extract it, then copy over your layers/ folder and src/config.js.

@ipv6freely I've had a PR open for months, Hashlips is too busy to properly review it.

Shocking…. Not.

He hasn’t even closed this GitHub Issue yet even though it’s long outdated and is filled with so much off topic junk discussion.

I’d love to see your changes merged. It’s way too easy to fork a repo and add malicious code, especially in the NFT space where most people have absolutely zero idea how to audit code. Having legit code merged is the best way to prevent that!

I’m sure I’m not telling you anything that isn’t obvious to you already ;)

I wouldn't be too sure, I'm not exactly an expert on this type of stuff.

On Sat, May 7, 2022, 4:02 PM Chris Jones @.> wrote: @CobraKaiX https://github.com/CobraKaiX you can get the zip https://github.com/bolshoytoster/hashlips_art_engine/archive/refs/heads/main.zip, extract it, then copy over your layers/ folder and src/config.js. @ipv6freely https://github.com/ipv6freely I've had a PR open for months, Hashlips is too busy to properly review it. Shocking…. Not. He hasn’t even closed this GitHub Issue yet even though it’s long outdated and is filled with so much off topic junk discussion. I’d love to see your changes merged. It’s way too easy to fork a repo and add malicious code, especially in the NFT space where most people have absolutely zero idea how to audit code. Having legit code merged is the best way to prevent that! I’m sure I’m not telling you anything that isn’t obvious to you already ;) — Reply to this email directly, view it on GitHub <#812 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX5PI56YJ2XKGMPBPGNCED3VI3ZA7ANCNFSM5PMRVF4Q . You are receiving this because you were mentioned.Message ID: @.>

I meant @bolshoytoster

I keep getting this error on both of my macs.
Uploading 8200D1FA-AF21-4C0F-A7A1-F6B7D0B2CB6B.jpeg…

Any help please?

Any help please?

This Issue thread is to address how to make nodejs work correctly on M1 based Macs. For unrelated questions I would suggest asking on Discord

I’m on a Mac. I have asked discord. I was hoping someone could help me. I know it’s something dumb. So you can’t help?

I’m on a Mac. I have asked discord. I was hoping someone could help me. I know it’s something dumb. So you can’t help?

Again, this thread is nodejs install issues on an M1 Mac. Your question is not in any way related.

Sorry thread nazi

An actual human helped me already

An actual human helped me already

Great. Now we can stop cluttering this thread with unrelated nonsense.

@CobraKaiX can you try using my fork please.

also, ipv6freely is quite defensive of this thread, you should keep it to M1 issues only.

@CobraKaiX can you try using my fork please.

also, ipv6freely is quite defensive of this thread, you should keep it to M1 issues only.

I honestly don’t care anymore. Seems hashlips couldn’t care less about it and all I get is crap for trying to stay on topic, so why bother helping anymore? I’m unfollowing this thread and locking the updated version one I made. I give up.

@ipv6freely next time I talk to HashLips I'll ask for permissions to close/lock issues.

npm ERR! Failed at the hashlips_art_engine@1.1.1 generate script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! Failed at the hashlips_art_engine@1.1.1 generate script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@funkymonkey5150 is that the whole error? If so, could you paste the output of running node index.js.

what do i have to do

10k-collection-video@2.0.0 generate
node index.js

node:fs:1450
handleErrorFromBinding(ctx);
^

Error: ENOENT: no such file or directory, scandir '/Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/layers/Background/'
at Object.readdirSync (node:fs:1450:3)
at getElements (/Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/src/main.js:73:6)
at /Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/src/main.js:89:15
at Array.map ()
at layersSetup (/Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/src/main.js:87:30)
at startCreating (/Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/src/main.js:352:20)
at /Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/index.js:6:3
at Object. (/Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/index.js:7:3)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10) {
errno: -2,
syscall: 'scandir',
code: 'ENOENT',
path: '/Users/elsygarcia/Downloads/create-10k-nft-collection-2.0.0/layers/Background/'
}

Node.js v18.7.0

@Angelje47 you need to save src/config.js.

Hello everyone,

I am trying to run the command "npm I" on my VScode terminal on a M1 Mac. Unfortunately, I keep having several errors that I don't understand even after trying what suggested in this thread : I am unable to solve it :

Capture d’écran 2022-08-24 à 16 45 34

Could anyone help me to solve this issue please ? Thank you very much in advance

@WissemEd did you run arch -arm64 brew install pkg-config cairo pango jpeg giflib librsvg?

You're also not using node v14.17.3

@bolshoytoster Do you think that I should use v14.17.3 only ? I am currently trying the most recent version

@WissemEd the original message in this issue says so.