linkedin / linkedin/qark

npm run generate error

Open
#387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3.4k
Forks
663
PR merge metrics
No merged PRs in 30d

Description

hey developers, i am getting this error whenever i tried to use command ''npm run generate'' i followed a youtube video each and every step but his command did work but I am not able to do it. Can anyone help me out, how can i resolve this error? Thanks!

hashlips_art_engine@1.1.1 generate
node index.js

(node:17356) [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)
F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\src\main.js:183
const image = await loadImage(${_layer.selectedElement.path});
^

TypeError: Cannot read properties of undefined (reading 'path')
at F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\src\main.js:183:61
at new Promise ()
at loadLayerImg (F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\src\main.js:182:10)
at F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\src\main.js:363:31
at Array.forEach ()
at startCreating (F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\src\main.js:362:17)
at F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\index.js:6:3
at Object. (F:\NFT\hashlips_art_engine-1.1.2_patch_v1\hashlips_art_engine-1.1.2_patch_v1\index.js:7:3)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report identifies npm run generate, index.js, and src/main.js lines 182-183 and 362-363 as the execution path. First verify whether those Node.js files and the reported command belong to this repository, then reproduce the error with the available project inputs; done means establishing a repository-specific cause and recording a confirmed resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.