Techy Things » node.js

Compiling node-canvas with Node 20 fails with ‘v8::AccessorSignature’ has not been declared

frank — Thu, 01 May 2025 18:06:28 +0000

/home/frank/.cache/node-gyp/20.19.0/include/node/v8-persistent-handle.h:498:14: warning: array subscript 0 is outside array bounds of ‘Nan::Persistent [0]’ [-Warray-bounds]
  498 |   this->val_ = New(isolate, internal::ValueHelper::ValueAsSlot(*other));
      |   ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CXX(target) Release/obj.target/canvas/src/backend/ImageBackend.o
  CXX(target) Release/obj.target/canvas/src/backend/PdfBackend.o
  CXX(target) Release/obj.target/canvas/src/backend/SvgBackend.o
  CXX(target) Release/obj.target/canvas/src/bmp/BMPParser.o
  CXX(target) Release/obj.target/canvas/src/Backends.o
  CXX(target) Release/obj.target/canvas/src/Canvas.o
In file included from ../src/Canvas.cc:21:
../src/Util.h: In function ‘void SetProtoAccessor(v8::Local, v8::Local, Nan::GetterCallback, Nan::SetterCallback, v8::Local)’:
../src/Util.h:25:21: error: ‘v8::AccessorSignature’ has not been declared
   25 |                 v8::AccessorSignature::New(v8::Isolate::GetCurrent(), ctor)
      |                     ^~~~~~~~~~~~~~~~~
make: *** [canvas.target.mk:159: Release/obj.target/canvas/src/Canvas.o] Error 1
make: Leaving directory '/home/frank/dev/health-planner/server/node_modules/node-canvas/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess. (/home/frank/.nvm/versions/node/v20.19.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)
gyp ERR! System Linux 6.1.0-32-amd64
gyp ERR! command "/home/frank/.nvm/versions/node/v20.19.0/bin/node" "/home/frank/.nvm/versions/node/v20.19.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/frank/dev/health-planner/server/node_modules/node-canvas

Solution #1

Revert to Node 18

Solution #2

I'm̀ still looking for one

The post Compiling node-canvas with Node 20 fails with ‘v8::AccessorSignature’ has not been declared appeared first on Techy Things.

node-canvas on Windows fails with Warning: Missing input files: C:\GTK\bin\libpangowin32-1.0-0.dll etc

frank — Mon, 21 Apr 2025 03:29:31 +0000

gyp info spawn args '-Dmodule_root_dir=C:\\dev\\health-planner\\server\\node_modules\\node-canvas',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'C:\\dev\\health-planner\\server\\node_modules\\node-canvas\\build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
Warning: Missing input files:
C:\GTK\bin\libpangowin32-1.0-0.dll
C:\GTK\bin\libgmodule-2.0-0.dll
C:\GTK\bin\libgthread-2.0-0.dll
C:\GTK\bin\libcairo-2.dll
C:\GTK\bin\libpangoft2-1.0-0.dll
C:\GTK\bin\libpango-1.0-0.dll
C:\GTK\bin\zlib1.dll
C:\GTK\bin\libpangocairo-1.0-0.dll
C:\GTK\bin\libglib-2.0-0.dll
C:\GTK\bin\libgobject-2.0-0.dll
C:\GTK\bin\libfontconfig-1.dll
C:\GTK\bin\libexpat-1.dll
C:\GTK\bin\libfreetype-6.dll
C:\GTK\bin\libpng14-14.dll
C:\GTK\bin\libintl-8.dll

Solution #1

Go on Linux, it doesnt have this problem.

Solution #2

Use canvas npm instead of node-canvas. This one works better.

Solution #3

Install GTK

The post node-canvas on Windows fails with Warning: Missing input files: C:\GTK\bin\libpangowin32-1.0-0.dll etc appeared first on Techy Things.

ValueError: invalid mode: 'rU' while trying to load binding.gyp

frank — Fri, 29 Mar 2024 02:49:30 +0000

Traceback (most recent call last):
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\gyp_main.py", line 51, in 
 sys.exit(gyp.script_main())
 ^^^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 670, in script_main
 return main(sys.argv[1:])
 ^^^^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 662, in main
 return gyp_main(args)
 ^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 629, in gyp_main
 [generator, flat_list, targets, data] = Load(
 ^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 150, in Load
 result = gyp.input.Load(
 ^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 3021, in Load
 LoadTargetBuildFile(
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 411, in LoadTargetBuildFile
 build_file_data = LoadOneBuildFile(
 ^^^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 239, in LoadOneBuildFile
 build_file_contents = open(build_file_path, "rU").read()
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: invalid mode: 'rU' while trying to load binding.gyp

Solution

Uninstall Python 3.12.X and install an older version like 3.10.X

The U file mode was removed in Python 3.11 because it had no effect so the U can merely be removed.

Python 3.10.11 was tested as working.

The post ValueError: invalid mode: 'rU' while trying to load binding.gyp appeared first on Techy Things.

gyp verb check python checking for Python executable "python2" in the PATH

frank — Wed, 30 Mar 2022 04:05:21 +0000

error C:\dev\react-scss-jest-typescript\node_modules\sass-jest\node_modules\node-sass: Command failed.
Exit code: 1
Command: node scripts/build.js
Arguments:
Directory: C:\dev\react-scss-jest-typescript\node_modules\sass-jest\node_modules\node-sass
Output:
Building: C:\Program Files\nodejs\node.exe C:\dev\react-scss-jest-typescript\node_modules\sass-jest\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli 'C:\\dev\\react-scss-jest-typescript\\node_modules\\sass-jest\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library='
gyp verb cli ]
gyp info using node-gyp@3.8.0
gyp info using node@16.14.2 | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed at getNotFoundError (C:\dev\react-scss-jest-typescript\node_modules\which\which.js:13:12)
gyp verb `which` failed at F (C:\dev\react-scss-jest-typescript\node_modules\which\which.js:68:19)
gyp verb `which` failed at E (C:\dev\react-scss-jest-typescript\node_modules\which\which.js:80:29)
gyp verb `which` failed at C:\dev\react-scss-jest-typescript\node_modules\which\which.js:89:16
gyp verb `which` failed at C:\dev\react-scss-jest-typescript\node_modules\isexe\index.js:42:5
gyp verb `which` failed at C:\dev\react-scss-jest-typescript\node_modules\isexe\windows.js:36:5
gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:198:21)
gyp verb `which` failed python2 Error: not found: python2
gyp verb `which` failed at getNotFoundError (C:\dev\react-scss-jest-typescript\node_modules\which\which.js:13:12)
gyp verb `which` failed at F (C:\dev\react-scss-jest-typescript\node_modules\which\which.js:68:19)
gyp verb `which` failed at E (C:\dev\react-scss-jest-typescript\node_modules\which\which.js:80:29)
gyp verb `which` failed at C:\dev\react-scss-jest-typescript\node_modules\which\which.js:89:16
gyp verb `which` failed at C:\dev\react-scss-jest-typescript\node_modules\isexe\windows.js:36:5
gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:198:21) {
gyp verb `which` failed code: 'ENOENT'
gyp verb `which` failed }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` succeeded python C:\Users\Domino\AppData\Local\Programs\Python\Python310\python.EXE
gyp ERR! configure error
gyp ERR! stack Error: Command failed: C:\Users\Domino\AppData\Local\Programs\Python\Python310\python.EXE -c import sys; print "%s.%s.%s" % sgyp ERR! stack File "", line 1
gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gyp ERR! stack SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
gyp ERR! stack
gyp ERR! stack at ChildProcess.exithandler (node:child_process:399:12)
gyp ERR! stack at ChildProcess.emit (node:events:526:28)
gyp ERR! stack at maybeClose (node:internal/child_process:1092:16)
gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
gyp ERR! System Windows_NT 10.0.19043
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\dev\\react-scss-jest-typescript\\node_modules\\sass-jest\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\dev\react-scss-jest-typescript\node_modules\sass-jest\node_modules\node-sass
gyp ERR! node -v v16.14.2

Solution

$ npm install --global windows-build-tools

If it hangs and fails, try

$ npm install --global --production windows-build-tools@4.0.0

The post gyp verb check python checking for Python executable "python2" in the PATH appeared first on Techy Things.

npm install fails with npm ERR! Unexpected token '.'

frank — Wed, 30 Mar 2022 02:56:52 +0000

Error

npm install -g yarn
npm ERR! Unexpected token '.'

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Domino\AppData\Local\npm-cache\_logs\2022-03-25-debug-0.log

Error with verbose on

(...)
npm verb stack C:\Users\Domino\AppData\Roaming\nvm\v16.14.2\node_modules\npm\node_modules\libnpmfund:1
npm verb stack ../workspaces/libnpmfund
npm verb stack ^
npm verb stack
npm verb stack SyntaxError: Unexpected token '.'
npm verb stack at Object.compileFunction (node:vm:352:18)
npm verb stack at wrapSafe (node:internal/modules/cjs/loader:1032:15)
npm verb stack at Module._compile (node:internal/modules/cjs/loader:1067:27)
npm verb stack at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
npm verb stack at Module.load (node:internal/modules/cjs/loader:981:32)
npm verb stack at Function.Module._load (node:internal/modules/cjs/loader:822:12)
npm verb stack at Module.require (node:internal/modules/cjs/loader:1005:19)
npm verb stack at require (node:internal/modules/cjs/helpers:102:18)
npm verb stack at Object. (C:\Users\Domino\AppData\Roaming\nvm\v16.14.2\node_modules\npm\lib\utils\reify-output.js:16:38)

Solution

This is due to a bug introduced in nvm 1.1.8.

It fails to ask for the windows elevated permission prompt (UAE).

~~The solution is either to downgrade to nvm 1.1.7, or enable Windows feature "Developer Mode" to ON.~~

The solution is to upgrade to nvm 1.1.10 where the elevated permission prompt is restored !

Problem #1 - exit status 5: Access is denied.

PS C:\dev\react-scss-jest-typescript> nvm uninstall 16.14.2
Uninstalling node v16.14.2...exit status 5: Access is denied.

This is another variation of the same bug.

I tried this and was not happy with the results as it would only partially fix the issues. So I don't recommend it:

$ Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

How to Install nvm

Latest installer for Windows: https://github.com/coreybutler/nvm-windows/releases

Latest installer for Linux/Mac: https://github.com/nvm-sh/nvm#install--update-script

Some people having same issues

https://github.com/npm/cli/issues/4234

https://stackoverflow.com/questions/70852727/unknown-error-on-npm-install-npm-err-unexpected-token-on-using-nvm-window

The post npm install fails with npm ERR! Unexpected token '.' appeared first on Techy Things.

On Node.js versions

frank — Thu, 23 Apr 2020 00:14:37 +0000

The Latest Nodes Releases for Majors Versions

Node 13, Node 12, Node 11, Node 10

https://nodejs.org/dist/latest-v13.x/

../
docs/                                              14-Apr-2020 16:47                   -
win-x64/                                           14-Apr-2020 16:35                   -
win-x86/                                           14-Apr-2020 16:35                   -
SHASUMS256.txt                                     14-Apr-2020 18:27                3147
SHASUMS256.txt.asc                                 14-Apr-2020 18:27                4029
SHASUMS256.txt.sig                                 14-Apr-2020 18:27                 566
node-v13.13.0-aix-ppc64.tar.gz                     14-Apr-2020 16:10            43019192
node-v13.13.0-darwin-x64.tar.gz                    14-Apr-2020 17:27            31348703
node-v13.13.0-darwin-x64.tar.xz                    14-Apr-2020 17:28            20222248
node-v13.13.0-headers.tar.gz                       14-Apr-2020 16:48              550225
node-v13.13.0-headers.tar.xz                       14-Apr-2020 16:48              366956
node-v13.13.0-linux-arm64.tar.gz                   14-Apr-2020 16:12            33395759
node-v13.13.0-linux-arm64.tar.xz                   14-Apr-2020 16:15            20227900
node-v13.13.0-linux-armv7l.tar.gz                  14-Apr-2020 16:15            31428176
node-v13.13.0-linux-armv7l.tar.xz                  14-Apr-2020 16:16            18638004
node-v13.13.0-linux-ppc64le.tar.gz                 14-Apr-2020 16:14            33390920
node-v13.13.0-linux-ppc64le.tar.xz                 14-Apr-2020 16:15            20568576
node-v13.13.0-linux-s390x.tar.gz                   14-Apr-2020 16:14            33873984
node-v13.13.0-linux-s390x.tar.xz                   14-Apr-2020 16:14            20526256
node-v13.13.0-linux-x64.tar.gz                     14-Apr-2020 16:13            33369132
node-v13.13.0-linux-x64.tar.xz                     14-Apr-2020 16:15            21283272
node-v13.13.0-sunos-x64.tar.gz                     14-Apr-2020 16:53            37837020
node-v13.13.0-sunos-x64.tar.xz                     14-Apr-2020 16:54            24174692
node-v13.13.0-win-x64.7z                           14-Apr-2020 16:35            16956562
node-v13.13.0-win-x64.zip                          14-Apr-2020 16:35            28151919
node-v13.13.0-win-x86.7z                           14-Apr-2020 16:39            15873405
node-v13.13.0-win-x86.zip                          14-Apr-2020 16:43            26615381
node-v13.13.0-x64.msi                              14-Apr-2020 16:35            29904896
node-v13.13.0-x86.msi                              14-Apr-2020 16:43            28266496
node-v13.13.0.pkg                                  14-Apr-2020 17:24            31681170
node-v13.13.0.tar.gz                               14-Apr-2020 16:41            61215472
node-v13.13.0.tar.xz                               14-Apr-2020 16:45            32862040

https://nodejs.org/dist/latest-v12.x/

../
docs/                                              08-Apr-2020 04:09                   -
win-x64/                                           08-Apr-2020 02:41                   -
win-x86/                                           08-Apr-2020 02:34                   -
SHASUMS256.txt                                     08-Apr-2020 19:25                3147
SHASUMS256.txt.asc                                 08-Apr-2020 19:25                4029
SHASUMS256.txt.sig                                 08-Apr-2020 19:25                 566
node-v12.16.2-aix-ppc64.tar.gz                     08-Apr-2020 16:24            32267957
node-v12.16.2-darwin-x64.tar.gz                    08-Apr-2020 17:00            20331548
node-v12.16.2-darwin-x64.tar.xz                    08-Apr-2020 17:01            13382680
node-v12.16.2-headers.tar.gz                       08-Apr-2020 16:57              548237
node-v12.16.2-headers.tar.xz                       08-Apr-2020 16:57              365416
node-v12.16.2-linux-arm64.tar.gz                   08-Apr-2020 16:26            23003145
node-v12.16.2-linux-arm64.tar.xz                   08-Apr-2020 16:28            13939796
node-v12.16.2-linux-armv7l.tar.gz                  08-Apr-2020 16:28            21202445
node-v12.16.2-linux-armv7l.tar.xz                  08-Apr-2020 16:29            12503028
node-v12.16.2-linux-ppc64le.tar.gz                 08-Apr-2020 16:27            23162733
node-v12.16.2-linux-ppc64le.tar.xz                 08-Apr-2020 16:28            13843368
node-v12.16.2-linux-s390x.tar.gz                   08-Apr-2020 16:28            23470105
node-v12.16.2-linux-s390x.tar.xz                   08-Apr-2020 16:28            13953480
node-v12.16.2-linux-x64.tar.gz                     08-Apr-2020 16:59            23116958
node-v12.16.2-linux-x64.tar.xz                     08-Apr-2020 17:00            14677200
node-v12.16.2-sunos-x64.tar.gz                     08-Apr-2020 17:21            27366342
node-v12.16.2-sunos-x64.tar.xz                     08-Apr-2020 17:22            16892496
node-v12.16.2-win-x64.7z                           08-Apr-2020 16:48            10817850
node-v12.16.2-win-x64.zip                          08-Apr-2020 16:48            18744085
node-v12.16.2-win-x86.7z                           08-Apr-2020 16:51             9758976
node-v12.16.2-win-x86.zip                          08-Apr-2020 16:51            17230009
node-v12.16.2-x64.msi                              08-Apr-2020 16:48            19763200
node-v12.16.2-x86.msi                              08-Apr-2020 16:52            18157568
node-v12.16.2.pkg                                  08-Apr-2020 17:12            20606508
node-v12.16.2.tar.gz                               08-Apr-2020 16:51            52267110
node-v12.16.2.tar.xz                               08-Apr-2020 16:55            23654020

https://nodejs.org/dist/latest-v11.x/

../
docs/                                              30-Apr-2019 17:39                   -
win-x64/                                           30-Apr-2019 04:45                   -
win-x86/                                           30-Apr-2019 04:38                   -
SHASUMS256.txt                                     30-Apr-2019 17:52                3347
SHASUMS256.txt.asc                                 30-Apr-2019 17:52                4229
SHASUMS256.txt.sig                                 30-Apr-2019 17:52                 566
node-v11.15.0-aix-ppc64.tar.gz                     30-Apr-2019 04:23            24795120
node-v11.15.0-darwin-x64.tar.gz                    30-Apr-2019 04:17            17791487
node-v11.15.0-darwin-x64.tar.xz                    30-Apr-2019 04:18            11834000
node-v11.15.0-headers.tar.gz                       30-Apr-2019 17:39              530668
node-v11.15.0-headers.tar.xz                       30-Apr-2019 17:39              354924
node-v11.15.0-linux-arm64.tar.gz                   30-Apr-2019 03:46            20221444
node-v11.15.0-linux-arm64.tar.xz                   30-Apr-2019 03:48            12495356
node-v11.15.0-linux-armv6l.tar.gz                  30-Apr-2019 04:14            19265450
node-v11.15.0-linux-armv6l.tar.xz                  30-Apr-2019 04:15            11582208
node-v11.15.0-linux-armv7l.tar.gz                  30-Apr-2019 04:55            19129403
node-v11.15.0-linux-armv7l.tar.xz                  30-Apr-2019 04:56            11522716
node-v11.15.0-linux-ppc64le.tar.gz                 30-Apr-2019 03:49            20619352
node-v11.15.0-linux-ppc64le.tar.xz                 30-Apr-2019 03:50            12580400
node-v11.15.0-linux-s390x.tar.gz                   30-Apr-2019 03:50            20672841
node-v11.15.0-linux-s390x.tar.xz                   30-Apr-2019 03:50            12348512
node-v11.15.0-linux-x64.tar.gz                     30-Apr-2019 04:29            20416954
node-v11.15.0-linux-x64.tar.xz                     30-Apr-2019 04:30            13234412
node-v11.15.0-sunos-x64.tar.gz                     30-Apr-2019 03:50            21623898
node-v11.15.0-sunos-x64.tar.xz                     30-Apr-2019 03:51            13706776
node-v11.15.0-win-x64.7z                           30-Apr-2019 04:46             9797160
node-v11.15.0-win-x64.zip                          30-Apr-2019 04:46            16616022
node-v11.15.0-win-x86.7z                           30-Apr-2019 04:38             8693995
node-v11.15.0-win-x86.zip                          30-Apr-2019 04:38            15110850
node-v11.15.0-x64.msi                              30-Apr-2019 04:47            17440768
node-v11.15.0-x86.msi                              30-Apr-2019 04:39            15843328
node-v11.15.0.pkg                                  30-Apr-2019 05:11            18032878
node-v11.15.0.tar.gz                               30-Apr-2019 17:32            48652148
node-v11.15.0.tar.xz                               30-Apr-2019 17:37            22115480

https://nodejs.org/dist/latest-v10.x/

../
docs/                                              12-Apr-2020 13:15                   -
win-x64/                                           10-Apr-2020 18:27                   -
win-x86/                                           10-Apr-2020 18:32                   -
SHASUMS256.txt                                     12-Apr-2020 13:24                3347
SHASUMS256.txt.asc                                 12-Apr-2020 13:24                3884
SHASUMS256.txt.sig                                 12-Apr-2020 13:24                 310
node-v10.20.1-aix-ppc64.tar.gz                     12-Apr-2020 11:46            25777574
node-v10.20.1-darwin-x64.tar.gz                    12-Apr-2020 12:19            19181761
node-v10.20.1-darwin-x64.tar.xz                    12-Apr-2020 12:19            12522440
node-v10.20.1-headers.tar.gz                       12-Apr-2020 12:02              539769
node-v10.20.1-headers.tar.xz                       12-Apr-2020 12:02              358264
node-v10.20.1-linux-arm64.tar.gz                   12-Apr-2020 11:49            21229063
node-v10.20.1-linux-arm64.tar.xz                   12-Apr-2020 11:51            12908388
node-v10.20.1-linux-armv6l.tar.gz                  12-Apr-2020 11:55            20159857
node-v10.20.1-linux-armv6l.tar.xz                  12-Apr-2020 11:56            11838492
node-v10.20.1-linux-armv7l.tar.gz                  12-Apr-2020 11:52            20016247
node-v10.20.1-linux-armv7l.tar.xz                  12-Apr-2020 11:53            11788356
node-v10.20.1-linux-ppc64le.tar.gz                 12-Apr-2020 11:51            21196960
node-v10.20.1-linux-ppc64le.tar.xz                 12-Apr-2020 11:52            12681216
node-v10.20.1-linux-s390x.tar.gz                   12-Apr-2020 11:51            21544747
node-v10.20.1-linux-s390x.tar.xz                   12-Apr-2020 11:52            12810988
node-v10.20.1-linux-x64.tar.gz                     12-Apr-2020 11:55            21286903
node-v10.20.1-linux-x64.tar.xz                     12-Apr-2020 11:56            13455784
node-v10.20.1-sunos-x64.tar.gz                     12-Apr-2020 11:56            22504428
node-v10.20.1-sunos-x64.tar.xz                     12-Apr-2020 11:56            13989352
node-v10.20.1-win-x64.7z                           12-Apr-2020 12:32            10603941
node-v10.20.1-win-x64.zip                          12-Apr-2020 12:32            18601692
node-v10.20.1-win-x86.7z                           12-Apr-2020 12:34             9511109
node-v10.20.1-win-x86.zip                          12-Apr-2020 12:35            17101353
node-v10.20.1-x64.msi                              12-Apr-2020 12:32            19484672
node-v10.20.1-x86.msi                              12-Apr-2020 12:38            17907712
node-v10.20.1.pkg                                  12-Apr-2020 12:26            19448064
node-v10.20.1.tar.gz                               12-Apr-2020 11:56            47181867
node-v10.20.1.tar.xz                               12-Apr-2020 12:00            21947588

The post On Node.js versions appeared first on Techy Things.

Debug NodeJS with Visual Studio Code on Windows and Linux

frank — Tue, 21 Jan 2020 18:33:40 +0000

Windows

Download Visual Studio Code
Download and Install Node.JS
Restart Visual Studio Code if it was opened
Create a dummy file to test like hello.js with this content :
In Visual Studio Code, open the folder containing this file above.
From the left side of Visual Studio Code, double-click the file hello.js
Click on the top bar menu "Debug". It should work.

Linux

This is a bit more tricky, but possible. The solution is to run an extra command-line to setup a SSH tunnel between the host (windows) and the target (linux)

Download Visual Studio Code
Download and Install Node.JS
Restart Visual Studio Code if it was opened
Create a test JS file to test like hello.js with this content :
Upload the JS file on the linux box
Run the JS file with debugger arguments:
WINDOWS: Open a SSH tunnel on the machien with Visual Studio Code
Open a cmd.exe prompt and type :
$ ssh -L 9229:127.0.0.1:9229 maik@remote-node-host

References

https://maikthulhu.github.io/2019-05-17-remote-debugging-node-vscode/

The post Debug NodeJS with Visual Studio Code on Windows and Linux appeared first on Techy Things.

../binding.cc:28:17: fatal error: zmq.h: No such file or directory

frank — Wed, 04 Dec 2019 18:50:36 +0000

../binding.cc:28:17: fatal error: zmq.h: No such file or directory

Solution

CentOS : sudo yum install -y zeromq-devel
Debian : sudo apt-get install libzmq3-dev

Full log of error

make: Entering directory `/home/frank/product/js/services/node_modules/zmq/build'
CXX(target) Release/obj.target/zmq/binding.o
../binding.cc:28:17: fatal error: zmq.h: No such file or directory
#include
^
compilation terminated.
make: *** [Release/obj.target/zmq/binding.o] Error 1
make: Leaving directory `/home/frank/product/js/services/node_modules/zmq/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/frank/.nvm/versions/node/v8.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 3.10.0-957.21.2.el7.x86_64
gyp ERR! command "/home/frank/.nvm/versions/node/v8.16.0/bin/node" "/home/frank/.nvm/versions/node/v8.16.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/frank/product/js/services/node_modules/zmq
gyp ERR! node -v v8.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zmq@2.15.3 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zmq@2.15.3 install 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! /home/frank/.npm/_logs/2019-12-04T18_43_12_657Z-debug.log

The post ../binding.cc:28:17: fatal error: zmq.h: No such file or directory appeared first on Techy Things.

readv() failed (104: Connection reset by peer) while reading upstream

frank — Mon, 04 Nov 2019 17:09:38 +0000

[error] 1528#1528: *599 readv() failed (104: Connection reset by peer) while reading upstream, client: 10.65.11.207, server: localhost, request: "POST /apis/v2/system/upgrade/upload HTTP/1.1", upstream: "http://127.0.0.1:8085/apis/v2/system/upgrade/upload", host: "10.65.11.219", referrer: "https://10.65.11.219/admin/update"

Understanding:

This message "(XXX: Connection reset by peer) while reading upstream" appears when the server backend initiates the disconnect. It is not the client that failed. Usually the server will have responded to the request with a more specific error message to help debug. In my case the response which could be viewed with Google Chrome Network Inspector was :

HTTP 400 Bad Request
"{"code":"BadRequest","message":"maxFileSize exceeded, received 209763252 bytes of file data"}"

Solution:

change
http_server.use(restify.plugins.bodyParser();
to
http_server.use(restify.plugins.bodyParser({maxFileSize: 5 * 1024 * 1024 * 1024})); // 5 GB

The post readv() failed (104: Connection reset by peer) while reading upstream appeared first on Techy Things.

NodeJS v8 "err": {"message": "fsReadFileAsync(...).then(...).then(...).catch(...).done is not a function",

frank — Fri, 22 Dec 2017 15:10:41 +0000

After upgrading code and libraries, you might run into

"err":{"message":"fsReadFileAsync(...).then(...).then(...).catch(...).done is not a function",

An example erroneous code

 const fsReadFileAsync = util.promisify(fs.readFile.bind(fs));
 const fsWriteFileAsync = util.promisify(fs.writeFile.bind(fs));

 // First apply changes to fstab
 fsReadFileAsync(this._fstabFilename, "utf8")
 .then(function (contents) {
  var modifiedContents =
  self._alterFstab(
  contents,
  networkStorage.active,
  networkStorage.host,
  networkStorage.remotePath);
  return fsWriteFileAsync(self._fstabFilename, modifiedContents);
 })

 // Save our settings unless there was an error applying fstab changes
 .then(function () {
  self._saveSettings(networkStorage, callback);
 })

 .catch(function (error) {
  Helpers.Log.Error({
   fstabPath: self._fstabFilename,
   settings: networkStorage,
   error: error.stack
  }, "Error applying changes to fstab");
  callback(Errors.InternalServer());
 }).done();

Solution

Remove .done()

This happens when upgrading from var QFS = require("q-io/fs"); to native util.promisify()

The post NodeJS v8 "err": {"message": "fsReadFileAsync(...).then(...).then(...).catch(...).done is not a function", appeared first on Techy Things.