Building Service - Can't resolve './Index.js'

Hi,

I am trying to build openZmeter based on the available docker. It fails, though:

/home/openZmeter/Service # make CONFIG=./Configs/openWRT_nanopi_air
Building version 'custom_20210822.1537'
Reading configuration from './Configs/openWRT_nanopi_air'
Building WEB interface
npm WARN deprecated libcipm@4.0.8: This module is no longer used. Please see @npmcli/arborist if you would like to build and reify package trees programmatically.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated axios@0.15.3: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated

> core-js-pure@3.16.2 postinstall /home/openZmeter/Service/WEB/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js:
> https://opencollective.com/core-js
> https://patreon.com/zloirock
> https://paypal.me/zloirock
> bitcoin: bc1qlea7544qtsmj2rayg0lthvza9fau63ux0fstcz

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)


> ejs@2.7.4 postinstall /home/openZmeter/Service/WEB/node_modules/ejs
> node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)


> vis-data@7.1.2 postinstall /home/openZmeter/Service/WEB/node_modules/vis-data
> opencollective postinstall || exit 0

sh: opencollective: not found

> vis-timeline@7.4.9 postinstall /home/openZmeter/Service/WEB/node_modules/vis-timeline
> opencollective postinstall || exit 0

sh: opencollective: not found
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN bootstrap-loader@1.3.3 requires a peer of extract-text-webpack-plugin@<2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN bootstrap-loader@1.3.3 requires a peer of node-sass@* but none is installed. You must install peer dependencies yourself.
npm WARN bootstrap-loader@1.3.3 requires a peer of resolve-url-loader@* but none is installed. You must install peer dependencies yourself.
npm WARN bootstrap-loader@1.3.3 requires a peer of sass-loader@* but none is installed. You must install peer dependencies yourself.
npm WARN vis-data@7.1.2 requires a peer of uuid@^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN vis-data@7.1.2 requires a peer of vis-util@^4.0.0 || ^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN vis-timeline@7.4.9 requires a peer of @egjs/hammerjs@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN vis-timeline@7.4.9 requires a peer of keycharm@^0.3.0 || ^0.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN vis-timeline@7.4.9 requires a peer of propagating-hammerjs@^1.4.0 || ^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN vis-timeline@7.4.9 requires a peer of vis-util@^3.0.0 || ^4.0.0 || ^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN vis-timeline@7.4.9 requires a peer of xss@^1.0.0 but none is installed. You must install peer dependencies yourself.

added 1289 packages from 1424 contributors and audited 1293 packages in 34.589s
found 16 vulnerabilities (15 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

Insufficient number of arguments or no entry found.
Alternatively, run 'webpack(-cli) --help' for usage info.


ERROR in Entry module not found: Error: Can't resolve './Index.js' in '/home/openZmeter/Service/WEB'
make: *** [Makefile:75: Tmp/openZmeter.js] Error 2
/home/openZmeter/Service #

How to solve?

Thanks

Note: tried both master and devel branches, it made no difference.

Hi,

You are right, i miss some files in commit. Im updating it. It will be uploaded in a few minutes. (In devel branch)

Hi @edu ,

Yes, it builds now. So, let me recap, to check if I understand what should be done next:

  • I just need to have a DeviceV1 or DeviceV2 connected via USB to a NanoPi running openWRT - Which NanoPi? (NanoPC & NanoPi). NanoPi Air as such does not seem to be available anymore…
  • Just copy (e.g. via ssh) openZmeter from /Service/Tmp/openWRT_nanopi_air in the docker image, into the NanoPi
  • Run copied openZmeter in the NanoPi
  • Access the NanoPi from a web browser

Am I right? All of your guidance, much appreciated.

Thanks and best regards.

Hi @jaranguren,

Thank you for your interest in the project. Please, can you post some details about your project or interests?
Regarding your questions, the answer are:

  • You should use NanoPi Neo Air
  • Yes
  • Yes
  • Use BT for the configuration, then access through wifi.

Hi @paco

Thanks for the answers. Let me now answer to you.

BTW, a comment. With all respect, your workflow / branch management seems a bit counterintuitive to me: “master” is where you have your work in progress, “devel” is where you have stable stuff that can be used immediately. To the best of my understanding, it is meant to be the other way around. Is there a reason for you to do it the way you do it?

Best regards and thanks!