ArduPilot / ArduPilot/UAVLogViewer
npm start error
- Dominant language
- JavaScript
- Stars
- 258
- Forks
- 296
- PR merge metrics
- No merged PRs in 30d
Description
Getting this error when running `npm start`:
```ERROR in ./src/tools/parsers/parser.worker.js (./node_modules/babel-loader/lib/index.js!./node_modules/eslint-loader/dist/cjs.js??ruleSet[1].rules[19]!./src/tools/parsers/parser.worker.js) 5:22-67
Module not found: Error: Can't resolve './JsDataflashParser/parser' in '/home/cyriel/software/UAVLogViewer/src/tools/parsers'
resolve './JsDataflashParser/parser' in '/home/cyriel/software/UAVLogViewer/src/tools/parsers'
using description file: /home/cyriel/software/UAVLogViewer/package.json (relative path: ./src/tools/parsers)
Field 'browser' doesn't contain a valid alias configuration
using description file: /home/cyriel/software/UAVLogViewer/package.json (relative path: ./src/tools/parsers/JsDataflashParser/parser)
no extension
Field 'browser' doesn't contain a valid alias configuration
/home/cyriel/software/UAVLogViewer/src/tools/parsers/JsDataflashParser/parser doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/home/cyriel/software/UAVLogViewer/src/tools/parsers/JsDataflashParser/parser.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/home/cyriel/software/UAVLogViewer/src/tools/parsers/JsDataflashParser/parser.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/home/cyriel/software/UAVLogViewer/src/tools/parsers/JsDataflashParser/parser.wasm doesn't exist
as directory
/home/cyriel/software/UAVLogViewer/src/tools/parsers/JsDataflashParser/parser doesn't exist
Child worker-loader /home/cyriel/software/UAVLogViewer/node_modules/babel-loader/lib/index.js!/home/cyriel/software/UAVLogViewer/node_modules/eslint-loader/dist/cjs.js??ruleSet[1].rules[19]!/home/cyriel/software/UAVLogViewer/src/tools/parsers/parser.worker.js compiled with 1 error
webpack 5.75.0 compiled with 1 error in 33884 ms```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running `npm start` and inspect `src/tools/parsers/parser.worker.js`, focusing on its `JsDataflashParser/parser` import and the reported resolution path. Check whether the referenced parser exists at the expected location; done means the development build completes without this module-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100