Kaydka aqoonta
Cillad-bixinta Zinnector®
Khaladaadka ay dadku dhab ahaan ula kulmaan Zinnector CLI iyo xalka mid walba: spawn EINVAL on Windows, digniinta npm ee EBADENGINE, node-gyp oo codsanaya Visual Studio on Node 26, EPERM inta lagu jiro rakibidda, runtime aan kici doonin, iyo deked (port) isticmaal ku jirta.
Khaladaha ay dadku dhab ahaantii kala kulmaan Zinnector® CLI, mid kasta macnihiisa, iyo sida loo hagaajiyo. Gelitaan kastaa wuxuu magacaabayaa qoraalka dhabta ah ee aad arki doonto, si aad boggan uga raadiso. Haddii kanadu a ചിത്ര uusan halkaan oolin, soco amarka guuldarraystay adoo isticmaalaya ZINNECTOR_DEBUG=1 oo fur arrin (issue) github.com/Zinn-Digital/zinnector/issues adoo wata wax soo saarka, node --versionkaaga iyo nidaamkaaga hawlgalka (operating system).
"spawn EINVAL" isla marka lagu aqbalo rakibaadda runtime-ka (Windows)
Cilad ku jirta Zinnector® 0.1.0 iyo 0.1.1. On Windows rakibaha runtime wuxuu waday npm.cmd magac ahaan, Node ayaana diiday inay dhaliso (spawn) fayl .cmd ah iyada oo aan lahayn qolof (shell) tan iyo hagaajinteeda CVE-2024-27980 - markaa rakibaaddu way burburtay hal ilbiriqsi ka dib markii aad jawaabtay Y. Lagu hagaajiyay 0.1.2: npm hadda waxaa loo wadaa sida node npm-cli.js, taas oo ah mid la mid ah madal kasta oo aan u baahnayn qolof. Soco npm install -g zinnector@latest, ka dibna mar labaad zinnector dev.
"npm WARN EBADENGINE" inta lagu jiro rakibaadda, ama "Zinnector® needs Node 24 or newer"
Node-kaagu waa ka da'weyn yahay 24. npm waxay daabacdaa digtoonida sababtoo ah xirmadu waxay ku dhawaaqaysaa engines: >=24.18.1; rakibaaddu way dhammaataa si kastaba ha ahaatee, laakiin zinnector ayaa markaas diidda inay bilowdo (exit code 78) halkii ay ka fashilmi lahayd meel wareerin badan oo dambe ah. Rakibi LTS-ka hadda jira ee ka yimid nodejs.org — winget install OpenJS.NodeJS.LTS on Windows, brew install node@24 on macOS — xaqiiji in node --version uu daabacayo v24 ama ka sarreeya, oo mar labaad rakibi Zinnector®.
"gyp ERR!", "Building from source with node-gyp", or "You need to install Visual Studio"
Runtime-ka WordPress wuxuu leeyahay qayb dhalasho (native module) oo binary-yada horay loo sii dhisay ay u jiraan Node 24 iyo 25 kaliya. Node ka sii cusub (26 iyo wixii ka dambeeya, laga bilaabo Sebtembar 2026) rakibaadiisu waxay ku noqotaa inay ka soo ururiso isha (source), taas oo mashiinka Windows-ka caadiga ah ku dhammaata codsi Visual Studio ah. Lagu hagaajiyay 0.1.2: Zinnector® waxay tan ogaataa ka hor intaysan soo dejisan wax walba waxayna soo dejisaa Node 24 oo loogu talagalay runtime-ka keliya — qiyaastii 30 MB, oo lagu xaqiijiyay checksums-ka nodejs.org — markaa waxba weligood lama ururiyo. Haddii aad weli aragto ka dib markii aad kor u qaaddo, soco zinnector dev --reset-runtime si rakibaaddii nus-dhammaatay ee hore loogu tuuro marka hore.
Digniinta "EPERM" ee ka timaada npm inta ay nadiifineyso (Windows)
Ku dhawaad mar walba waa iska-cudurrada fayraska (antivirus scanner) ama tusaha raadinta (search indexer) oo haysta fayl furan oo hoos yimaada node_modules ee runtime-ka halka npm ay isku dayayso inay ka saarto. Rakibaadda ayaa dib loogu daydaa buug-gacmeed nadiif ah (clean directory) marka xigta zinnector dev; haddii ay sii wado inay dhacdo, zinnector dev --reset-runtime waxay ka saartaa buug-gacmeedka runtime-ka oo dhan marka hore oo dib bay u rakibtaa.
"the local playground runtime could not be installed"
Fariintu waxaa ku jira sadarrada u dambeeya ee npm iyo amarka saxda ah ee Zinnector® uu waday, si aad adigu u wadi kartid oo aad u aragto wax soo saarka buuxa. Sababaha caadiga ah waa dhibaato shabakad ama wakiil (proxy) ah — runtime-ka waxaa lagu soo dejiyaa npm-kaaga gaarka ah, markaa npm config set proxy … iyo muraayad diiwaangelin (registry mirror) ayaa quus ah — ama rakibaad hore oo nus-dhammaatay, taas oo --reset-runtime ay nadiifiso.
"the local playground exited before it was ready", ama weligeed ma diyaar garowdo
Soco zinnector dev --verbose si aad u aragto wax soo saarka runtime-ka. Deked hore loo isticmaalay waa tan caadiga ah: zinnector dev --port 9401, ama deji port gudaha zinnector.json. Runtime rakibay laakiin aan kabixi doonin: zinnector dev --reset-runtime. Kabashada ugu horreysa sidoo kale waxay soo dejisaa WordPress lafteeda, markaa xiriir gaabis ah sii dhowr daqiiqo; CLI waxay sugaysaa ilaa shan ka hor intaysan soo sheegin waqtiga dhammaaday (timeout) halkii ay sudhnaan lahayd.
"this project is not a git repository" markaad riixeyso (push)
Geynta (deploys) waxaa laga wadaa kayd (repository), markaa zinnector push waxay u baahan tahay mid leh fog (remote) oo madashu ay gaari karto. git init && git add -A && git commit -m initial, ku dar GitHub ama GitLab remote-kaaga, ka dibna zinnector link si aad ugu xirto bogga.
Goobtu waa caddaan dib u dejin ka dib
Soco zinnector check. Sagaal jeer tobankii waa farqiga nooca PHP — waxaad ku dhistay PHP ka cusub kan boosku (slot) wado — warbixintuna waxay leedahay nooca lagu beddelayo booska leh zinnector php <version>, ama kan lagu horumarinayo leh zinnector dev --php <version>. zinnector logs --error waxay tusaysaa dhimashada (fatal) lafteeda.
La xiriira
Weli waad daahday?
Taageero waxaa lagu daray qorshe kasta waxaana lagugu soo jawaabayaa luqadaada.
La xiriir taageerada → Maqaallada oo dhan →