brownhci/WebGazer

Webgazer with Encore

Open

#247 创建于 2021年11月17日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)HTML (3,412 star) (520 fork)batch import
help wanted

描述

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.

贡献者指南

技术栈
javascriptnodejs
领域
toolingbuild system
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of npm packagesBasic knowledge of webpack bundling
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
The issue reports missing imports in webgazer v2.1.0's src/index.mjs, such as './params', './dom util', etc. To resolve, first check if these files exist in the published npm package by comparing the package's src directory with the imports. If missing, the package may need to be rebuilt or republished. Look at the package.json to see if the 'files' field is missing these source files, or if the build process (webpack.config.js) incorrectly excludes them. The maintainer should verify the version 2.1.0's integrity and possibly add the missing files to the npm package.