Madogarar ilimi
Gyara matsalar Zinnector®
Kuskuren da mutane ke fuskanta a aikace tare da Zinnector CLI da kuma mafita ga kowannensu: spawn EINVAL a Windows, gargadin EBADENGINE na npm, node-gyp da ke neman Visual Studio a Node 26, EPERM yayin shigarwa, gudanarwar da ke kin tashi, da kuma port da ake amfani da shi.
Kurakunan da mutane ke fuskanta tare da Zinnector® CLI, ma'anar kowanne, da kuma hanyar gyara su. Kowane shigarwa yana nunainihin rubutun da zaku gani, ta yadda zaku iya binciken wannan shafin don samunsa. Idan naku bai nan, ku gudanar da umarnin da ya gaza tare da ZINNECTOR_DEBUG=1 sannan ku buɗe matsala a github.com/Zinn-Digital/zinnector/issues tare da sakamakon fitarwa, node --version naku da tsarin operating system naku.
"spawn EINVAL" nan take bayan karɓar shigarwar lokacin aiki (Windows)
Wani matsala a Zinnector® 0.1.0 da 0.1.1. A kan Windows mai sakawa lokacin aiki ya gudanar da npm.cmd ta suna, kuma Node ta ki ƙin ɗaukar fayil din .cmd ba tare da shell ba tun bayan gyara ta ga CVE-2024-27980 — don haka shigarwar ta fadi da sakan ɗaya bayan kun amsa da Y. An gyara a 0.1.2: yanzu ana gudanar da npm azaman node npm-cli.js, wanda yake iri ɗaya ne a kowane dandamali kuma baya buƙatar shell. Ku gudanar da npm install -g zinnector@latest, sannan zinnector dev kuma.
"npm WARN EBADENGINE" yayin shigarwa, ko "Zinnector® needs Node 24 or newer"
Node ɗinku ya fi 24 tsufa. npm tana buga gargaɗin saboda fakitin yana bayyana engines: >=24.18.1; shigarwar tana kammalawa duk da haka, amma zinnector tana ƙin farawa (lambar fitarwa 78) maimakon ta gaza a wani wuri mai rikitarwa anjima. Ku shigar da LTS na yanzu daga nodejs.org — winget install OpenJS.NodeJS.LTS a kan Windows, brew install node@24 a kan macOS — ku tabbatar node --version tana buga v24 ko mafi girma, kuma ku sake shigar da Zinnector®.
"gyp ERR!", "Building from source with node-gyp", ko "You need to install Visual Studio"
Lokacin aikin WordPress yana da wani tsarin asali wanda samfuransa da aka riga aka gina suna wanzu don Node 24 da 25 kawai. A kan sabon Node (26 da sama, tun daga Satumba 2026) mai sakawarsa yana komawa ga haɗawa daga tushe, wanda a kan injin Windows na yau da kullum yana kawo buƙatar Visual Studio. An gyara a 0.1.2: Zinnector® tana gano wannan kafin zazzage komai kuma tana ɗauko Node 24 don lokacin aiki kaɗai — kusan MB 30, an tabbatar da ita bisa ga lambobin checksum na nodejs.org — ta yadda ba a taɓa haɗa komai ba. Idan har yanzu kuna ganinta bayan kun ɗaga sigar, ku gudanar da zinnector dev --reset-runtime ta yadda shigarwar da ta riga ta tsaya rabuwa da ita daga baya za a jefa ta farko.
"EPERM" gargaɗi daga npm yayin da take tsaftacewa (Windows)
Kusan koda yaushe mai binciken riga-kafi ko mai binciken fihirisa na bincike yana riƙe da fayil a buɗe ƙarƙashin node_modules na lokacin aiki yayin da npm ke ƙoƙarin cire shi. Ana sake gwada shigarwar daga kundin adireshin mai tsabta a gaba zinnector dev; idan ta ci gaba da faruwa, zinnector dev --reset-runtime tana cire dukan kundin adireshin lokacin aiki da farko kuma tana sake shigarwa.
"the local playground runtime could not be installed"
Sako ya haɗa da layukan ƙarshe na npm kanta da ainihin umarnin da Zinnector® ta gudanar, ta yadda zaku iya gudanar da shi da kanku kuma ku ga cikakken fitarwa. Abubuwan da suka saba haifar da hakan sune matsalar hanyar sadarwa ko wakili (proxy) — ana zuƙo lokacin aiki tare da naku npm, don haka npm config set proxy … da madubin rajista sun shafi hakan — ko kuma tsohuwar shigarwar da ta tsaya rabuwa da ita wacce --reset-runtime ke sharewa.
"the local playground exited before it was ready", ko kuma bata taɓa zama a shirye ba
Ku gudanar da zinnector dev --verbose don ganin fitarwar lokacin aiki kanta. Tashar jiragen ruwa da aka riga aka yi amfani da ita ita ce mafi yawanci: zinnector dev --port 9401, ko sanya port a cikin zinnector.json. Lokacin aiki da aka shigar amma bazai tashi ba: zinnector dev --reset-runtime. Farko tashi kuma yana zazzage WordPress kanta, don haka a kan jinkirin haɗin gwiwa ku ba shi 'yan mintuna kaɗai; CLI tana jira har zuwa biyar kafin ta ba da rahoton ƙare lokaci maimakon ta rataye.
"this project is not a git repository" a kan turawa
Ana gudanar da tura kayayyaki daga ma'ajiyar bayanai, don haka zinnector push tana buƙatar ɗaya tare da nesa wanda dandamalin zai iya isa gare shi. git init && git add -A && git commit -m initial, ƙara GitHub ko GitLab nesa naka, sannan zinnector link don haɗa shi da shafin.
Shafin yana da fari bayan turawa
Ku gudanar da zinnector check. Sau tara cikin goma tazara ce ta sigar PHP — kun gina akan sabon PHP fiye da yadda ramin yake gudana — kuma rahoton yana nuna wace sigar za a canza ramin zuwa gare ta tare da zinnector php <version>, ko wace za a ɓullo da ita tare da zinnector dev --php <version>. zinnector logs --error tana nuna matsalar kanta.
Mai nasaba
Kuna nan makale?
An haɗa da tallafi a kowane tsari kuma ana ba da amsa a cikin harshenka.
Tuntuɓi tallafi → Dukkan labarai →