CODEWITHSUNDEEP
c++node.jscnode-addon-api
F22lightning
F22lightning

Reputation: 640

Problems running Napi on linux with callbackInfo

When using windows the Napi and I run npm i it compiles and works just fine. When doing the same on linux I get this error with the napi-inl.h

project/node_modules/node-addon-api/napi-inl.h: In instantiation of ‘static Napi::Function Napi::Function::New(napi_env, Callable, const char*, void*) [with Callable = Napi::Promise (*)(Napi::CallbackInfo&); napi_env = napi_env__*]’:
../test.cc:10:50:   required from here
project/node_modules/node-addon-api/napi-inl.h:1985:22: error: cannot bind non-const lvalue reference of type ‘Napi::CallbackInfo&’ to an rvalue of type ‘Napi::CallbackInfo’
 1985 |   typedef decltype(cb(CallbackInfo(nullptr, nullptr))) ReturnType;
      |                    ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
project/node_modules/node-addon-api/napi-inl.h:1985:22: error: cannot bind non-const lvalue reference of type ‘Napi::CallbackInfo&’ to an rvalue of type ‘Napi::CallbackInfo’
project/node_modules/node-addon-api/napi-inl.h:1996:5: error: type ‘<type error>’ argument given to ‘delete’, expected pointer
 1996 |     delete callbackData;
      |     ^~~~~~

test.cc looks like this

#include <napi.h>
#include "processData.h"


// This is were the Node module function name is assigned
// when imported getData() will be the function to call
// It calls Process()
Napi::Object Init(Napi::Env env, Napi::Object exports) {
  exports.Set(Napi::String::New(env, "getData"),
              Napi::Function::New(env, Process));
  return exports;
}

NODE_API_MODULE(NODE_GYP_MODULE_NAME, Init)

I don't know if this is an issue with me or with NAPI

Upvotes: 1

Views: 584

Answers (2)

F22lightning
F22lightning

Reputation: 640

Discovered that the problem was a simple mistake involving the function declaration in Process.cc missing the const keyword

old way:

Napi::Promise Process(Napi::CallbackInfo& info)

new way:

Napi::Promise Process(const Napi::CallbackInfo& info)

Upvotes: 1

Caio Francisco
Caio Francisco

Reputation: 26

It's because npm i are different on both Windows and Linux. Quoting an answer to another question:

Yes, there can be differences, say, if you (or your dependencies) use native node.js addons, which are built e.g. by node-gyp and contain native binary code. Also there can be OS/CPU - specific stuff in package.json. package.json description can be found here: https://docs.npmjs.com/files/package.json

Upvotes: 0

Related Questions