brownhci/WebGazer

Webgazer with Encore

Open

#247 opened on Nov 17, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)HTML (520 forks)batch import
help wanted

Repository metrics

Stars
 (3,412 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I have problem with install the newest version of webgazer (v2.1.0) via npm. When i try to compile the assets npm run dev

I have this Issue:

Module build failed: Module not found:
"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./params".
This file can not be found, please check it for typos or update it if the file got moved.

"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./dom_util".
This file can not be found, please check it for typos or update it if the file got moved.

"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./facemesh".
This file can not be found, please check it for typos or update it if the file got moved.

"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./ridgeReg".
This file can not be found, please check it for typos or update it if the file got moved.

"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./ridgeWeightedReg".
This file can not be found, please check it for typos or update it if the file got moved.

"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./ridgeRegThreaded".
This file can not be found, please check it for typos or update it if the file got moved.

"./node_modules/webgazer/src/index.mjs" contains a reference to the file "./util".
This file can not be found, please check it for typos or update it if the file got moved.

Contributor guide

Research direction
Investigate the missing file references in webgazer/src/index.mjs. Check if the files './params', './dom util', './facemesh', './ridgeReg', './ridgeWeightedReg', './ridgeRegThreaded', and './util' exist in the package. Look at the npm registry for webgazer v2.1.0 to see if the package is published correctly. Compare with an earlier version that works. Also check the package's package.json for the main field or exports.
Tech stack
javascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60