I have successfully installed Tidbyt on a 65bit linux box for testing. I am now trying to get it up and running on a raspberrypi that I have. I run the build command and get the following error.
I have removed everything and tried again and still the same error. I have copied the source entire fold of source files from the working linux distro and it still gives the same error.
That error indicates that the frontend devtools have not been built. You’ll need to install the frontend dependencies. Run the following before you make build:
So I ran the above, thought I had run it last night but must have not been paying attention.
Here is the error.
npm run build
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can’t make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
[webpack-cli] HookWebpackError: Not supported
at makeWebpackError (/home/homeseer/pixlet/pixlet/node_modules/webpack/lib/H ookWebpackError.js:48:9)
at hooks.processAssets.callAsync.err (/home/homeseer/pixlet/pixlet/node_modu les/webpack/lib/Compilation.js:3058:12)
at eval (eval at create (/home/homeseer/pixlet/pixlet/node_modules/tapable/l ib/HookCodeFactory.js:33:10), :70:1)
at err (/home/homeseer/pixlet/pixlet/node_modules/webpack/lib/Compilation.js :509:26)
at compilation.hooks.processAssets.tapAsync (/home/homeseer/pixlet/pixlet/no de_modules/copy-webpack-plugin/dist/index.js:708:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
– inner error –
Error: Not supported
at compilation.hooks.processAssets.tapAsync (/home/homeseer/pixlet/pixlet/no de_modules/copy-webpack-plugin/dist/index.js:704:13)
at fn (/home/homeseer/pixlet/pixlet/node_modules/webpack/lib/Compilation.js: 508:9)
at Hook.eval [as callAsync] (eval at create (/home/homeseer/pixlet/pixlet/no de_modules/tapable/lib/HookCodeFactory.js:33:10), :68:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/home/homeseer/pixlet/pixlet/no de_modules/tapable/lib/Hook.js:18:14)
at cont (/home/homeseer/pixlet/pixlet/node_modules/webpack/lib/Compilation.j s:3055:34)
at createChunkAssets.err (/home/homeseer/pixlet/pixlet/node_modules/webpack/ lib/Compilation.js:3103:10)
at symbolIterator (/home/homeseer/pixlet/pixlet/node_modules/neo-async/async .js:3485:9)
at done (/home/homeseer/pixlet/pixlet/node_modules/neo-async/async.js:3527:9 )
at /home/homeseer/pixlet/pixlet/node_modules/neo-async/async.js:2830:7
at done (/home/homeseer/pixlet/pixlet/node_modules/neo-async/async.js:2865:1 1)
caused by plugins in Compilation.hooks.processAssets
Error: Not supported
at compilation.hooks.processAssets.tapAsync (/home/homeseer/pixlet/pixlet/no de_modules/copy-webpack-plugin/dist/index.js:704:13)
at fn (/home/homeseer/pixlet/pixlet/node_modules/webpack/lib/Compilation.js: 508:9)
at Hook.eval [as callAsync] (eval at create (/home/homeseer/pixlet/pixlet/no de_modules/tapable/lib/HookCodeFactory.js:33:10), :68:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/home/homeseer/pixlet/pixlet/no de_modules/tapable/lib/Hook.js:18:14)
at cont (/home/homeseer/pixlet/pixlet/node_modules/webpack/lib/Compilation.j s:3055:34)
at createChunkAssets.err (/home/homeseer/pixlet/pixlet/node_modules/webpack/ lib/Compilation.js:3103:10)
at symbolIterator (/home/homeseer/pixlet/pixlet/node_modules/neo-async/async .js:3485:9)
at done (/home/homeseer/pixlet/pixlet/node_modules/neo-async/async.js:3527:9 )
at /home/homeseer/pixlet/pixlet/node_modules/neo-async/async.js:2830:7
at done (/home/homeseer/pixlet/pixlet/node_modules/neo-async/async.js:2865:1 1)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] build: webpack --config webpack.prod.js
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional log ging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-03-02T14_57_22_762Z-debug.log
More information: Cleaned up NPM and rebuilt. Started and got this error.
npm start
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can’t make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
SyntaxError: Unexpected token =
at Module._compile (internal/modules/cjs/loader.js:723:23)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Server.getServerTransport (/home/homeseer/pixlet/pixlet/node_modules/webpack-dev-server/lib/Server.js:1663:28)
at Server.createWebSocketServer (/home/homeseer/pixlet/pixlet/node_modules/webpack-dev-server/lib/Server.js:2443:57)
at Server.start (/home/homeseer/pixlet/pixlet/node_modules/webpack-dev-server/lib/Server.js:3229:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] start: webpack serve --config webpack.dev.js
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-03-02T15_21_44_525Z-debug.log
I have another webservice running on this machine, but not on this port. How can I run both? Am I heading in the right direction?
OK… I got through the last error by updating NPM and NodeJS. I then re-ran the commands you stated with no errors. Ran the “make build” still get the same thing.
root@HTPiHubG2v1:/home/homeseer/pixlet/pixlet# npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient…
npm WARN old lockfile
up to date, audited 699 packages in 48s
102 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
root@HTPiHubG2v1:/home/homeseer/pixlet/pixlet# npm run build
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
main.b8c9f1962a3849c12508.js (1.97 MiB)
WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
main (1.97 MiB)
main.b8c9f1962a3849c12508.js
WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit Code Splitting | webpack
webpack 5.69.1 compiled with 3 warnings in 155733 ms
root@HTPiHubG2v1:/home/homeseer/pixlet/pixlet# make build
rm -f pixlet
rm -rf ./build
rm -rf ./out
go build -o pixlet tidbyt.dev/pixlet
build tidbyt.dev/pixlet: cannot find module for path embed
make: *** [Makefile:20: build] Error 1
root@HTPiHubG2v1:/home/homeseer/pixlet/pixlet#
So for the other instance I have up and running I just copied the binary file from the download and did not build it myself. I am getting a similar error when trying to build on the system where it is working. This leads me to something in the source files that may be conflicting. I’m just lost at this point.
OK. So I went in and cleaned up some duplicate Go installations. I then went and updated the PATH with the correct go install. Manually installed embed.go and then re-ran make build. All worked. Very strange. This was a 10 hour journey.