msgpackr-extract@3.0.0 install /var/www/websites/stpaulalumniapi.cybraintech.com/node_modules/msgpackr-extract node-gyp-build-optional-packages
make: Entering directory '/var/www/websites/stpaulalumniapi.cybraintech.com/node_modules/msgpackr-extract/build'
CXX(target) Release/obj.target/extract/src/extract.o
../src/extract.cpp: In member function ‘napi_value__* Extractor::extractStrings(napi_env, int, int, uint8_t*)’:
../src/extract.cpp:165:121: error: no matching function for call to ‘v8::Array::New(v8::Isolate*, v8::Local<v8::Value>, int&)’
165 | v8::Local<v8::Array> v8Array = v8::Array::New(v8::Isolate::GetCurrent(), (v8::Local<v8::Value>) target, writePosition);
| ^
In file included from ../src/extract.cpp:10:
/usr/include/nodejs/deps/v8/include/v8.h:3674:23: note: candidate: ‘static v8::Local<v8::Array> v8::Array::New(v8::Isolate*, int)’
3674 | static Local New(Isolate* isolate, int length = 0);
| ^~~
/usr/include/nodejs/deps/v8/include/v8.h:3674:23: note: candidate expects 2 arguments, 3 provided
../src/extract.cpp:166:3: error: ‘memcpy’ was not declared in this scope
166 | memcpy(&array, &v8Array, sizeof(array));
| ^~~~~~
../src/extract.cpp:11:1: note: ‘memcpy’ is defined in header ‘’; did you forget to ‘#include ’?
10 | #include <v8.h>
+++ |+#include
11 | #endif
make: *** [extract.target.mk:119: Release/obj.target/extract/src/extract.o] Error 1
make: Leaving directory '/var/www/websites/stpaulalumniapi.cybraintech.com/node_modules/msgpackr-extract/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/share/nodejs/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 5.13.0-1029-aws
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /var/www/websites/stpaulalumniapi.cybraintech.com/node_modules/msgpackr-extract
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v6.1.0
gyp ERR! not ok
Team may want to consider filing a bug report with the package's maintainers. Alternatively, Suggest some currect packages version for nest js cli 8+ and 9+
