Kitty-items marketplace is not starting on testnet

Hi.
We want to review kitty-items marketplace. We installed env. tools and then we want to start on dev testnet. We took an error like this:

⠖ Deploying contracts to:  0xf8d6e0586b0a20c7 (emulator)node:internal/errors:841
  const err = new Error(message);
              ^

Error: Command failed: flow project deploy -o json --network=emulator -f flow.json --update
 Command Error: failed to deploy all contracts
    at ChildProcess.exithandler (node:child_process:398:12)
    at ChildProcess.emit (node:events:527:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'flow project deploy -o json --network=emulator -f flow.json --update',
  stdout: '\n',
  stderr: ' Command Error: failed to deploy all contracts'
}

Is there any one for help us. But I asked this question approximately 10 days ago.

after cloning with git:

git clone https://github.com/onflow/kitty-items.git

cd kitty-items

then

git checkout 7bfa03639d1ed3e77e1e3dd18be45576ab43577d

then it should work.

Firtsty thanks for your support @bluesign.

Contracts deployed. But did not work yet.

Our next problem is continuing. It is not fixed on github issues.

Do you know any information for this error?

We took this error:

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".CMD" for D:\SOURCES\FLOW\KITTY-ITEMS\KITTY-ITEMS\NODE_MODULES\.BIN\NPM.CMD
0|api    |     at new NodeError (node:internal/errors:372:5)
0|api    |     at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:76:11)
0|api    |     at defaultGetFormat (node:internal/modules/esm/get_format:118:38)
0|api    |     at defaultLoad (node:internal/modules/esm/load:21:20)
0|api    |     at ESMLoader.load (node:internal/modules/esm/loader:407:26)
0|api    |     at ESMLoader.moduleProvider (node:internal/modules/esm/loader:326:22)
0|api    |     at new ModuleJob (node:internal/modules/esm/module_job:66:26)
0|api    |     at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:345:17)
0|api    |     at ESMLoader.getModuleJob (node:internal/modules/esm/loader:304:34)
0|api    |     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
0|api    |   code: 'ERR_UNKNOWN_FILE_EXTENSION'
0|api    | }
PM2      | App [api:0] online
PM2      | App [api:0] exited with code [0] via signal [SIGINT]
PM2      | App [api:0] starting in -fork mode-
0|api    | TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".CMD" for D:\SOURCES\FLOW\KITTY-ITEMS\KITTY-ITEMS\NODE_MODULES\.BIN\NPM.CMD
0|api    |     at new NodeError (node:internal/errors:372:5)
0|api    |     at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:76:11)
0|api    |     at defaultGetFormat (node:internal/modules/esm/get_format:118:38)
0|api    |     at defaultLoad (node:internal/modules/esm/load:21:20)
0|api    |     at ESMLoader.load (node:internal/modules/esm/loader:407:26)
0|api    |     at ESMLoader.moduleProvider (node:internal/modules/esm/loader:326:22)
0|api    |     at new ModuleJob (node:internal/modules/esm/module_job:66:26)
0|api    |     at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:345:17)
0|api    |     at ESMLoader.getModuleJob (node:internal/modules/esm/loader:304:34)
0|api    |     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
0|api    |   code: 'ERR_UNKNOWN_FILE_EXTENSION'
0|api    | }

After contracts deployed, just start 2 powershelgl windows. And start api and web manually.

  • npx dotenv-cli -e .env.testnet – npm run dev --prefix api

  • npx dotenv-cli -e .env.testnet – npm run dev --prefix web

This workaround should help for now.

I am so newbie.
I apologise for my questions.

I entered that shell command to terminal and then occured that error:

npm ERR! Missing script: "dev"
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:

How can I solve this?

Are you using powershell? I tried on powershell the command.

Also no worries, we all have started as newbies

image_2022-06-02_145722595

Before npm double dash

Forum is mixing it to Unicode single long dash.

image_2022-06-02_152205227

inside web directory:

npm i @next/swc-win32-x64-msvc

I am so sorry. I so tired you. But I could not run.

image

{

  "name": "kitty-items",

  "version": "1.0.0",

  "description": "<p align=\"center\"><img width=\"400\" src=\"kitty-items-banner.png\" /></a> </p>",

  "type": "module",

  "dependencies": {

    "@next/swc-win32-x64-msvc": "^11.1.2",

    "chalk": "^5.0.0",

    "chalk-animation": "^2.0.2",

    "cross-env": "^7.0.3",

    "dotenv": "^16.0.0",

    "fs-jetpack": "^4.3.1",

    "gradient-string": "^2.0.0",

    "inquirer": "^8.2.0",

    "ora": "^6.1.0",

    "pm2": "^5.1.2",

    "yargs": "^16.2.0"

  },

  "devDependencies": {

    "@types/node": "^14.14.37",

    "@types/yargs": "^16.0.1",

    "dotenv-cli": "^5.1.0",

    "kill-port-process": "^3.0.1",

    "lerna": "^4.0.0",

    "npm": "^8.5.5"

  },

  "scripts": {

    "preinstall": "node .ki-scripts/version-check.js",

    "dev:emulator": "npx cross-env CHAIN_ENV=emulator node .ki-scripts/startup.js",

    "dev:testnet": "npx cross-env CHAIN_ENV=testnet node .ki-scripts/startup.js",

    "update:emulator": "flow project deploy --update",

    "update:testnet": "npx dotenv-cli -e .env.testnet -- flow project deploy --network=testnet -f flow.json -f flow.testnet.json --update",

    "dev:reset": "cross-env node .ki-scripts/reset.js",

    "postinstall": "npx lerna exec npm install"

  },

  "repository": {

    "type": "git",

    "url": "git+https://github.com/onflow/kitty-items.git"

  },

  "author": "",

  "license": "Apache 2",

  "bugs": {

    "url": "https://github.com/onflow/kitty-items/issues"

  },

  "homepage": "https://github.com/onflow/kitty-items#readme",

  "engines": {

    "node": "16.x"

  }

}

@bluesign Thanks for everything. I solved my all problems for your helps.

I deleted nodemodules in web folder. All errors gone. :slight_smile: