Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

Update dtrace-provider dependency from 0.6.0 to 0.8.8 #583

Closed
rod4n4m1 opened this issue Dec 2, 2019 · 2 comments
Closed

Update dtrace-provider dependency from 0.6.0 to 0.8.8 #583

rod4n4m1 opened this issue Dec 2, 2019 · 2 comments

Comments

@rod4n4m1
Copy link

rod4n4m1 commented Dec 2, 2019

Folks, unfortunately the old dtrace-provider@0.6.0 doesn't work on MacOS Catalina with the following error thread:

{ Error: Cannot find module './build/Release/DTraceProviderBindings'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)

If you export V you can see this detail when it's installing dtrace-provider@0.6.0:

../dtrace_provider.cc:89:35: error: no matching member function for call to 'NewInstance'
    v8::Local<Object> pd = klass->NewInstance();

And this causes a nasty error when rebuilding it.

5 warnings and 1 error generated.
make: *** [Release/obj.target/DTraceProviderBindings/dtrace_provider.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:193: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 Darwin 19.0.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/rodanami/sandbox/node_modules/ldapjs/node_modules/dtrace-provider
gyp ERR! node -v v10.17.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok 

To overcome this issue I had to use npm shrinkwrap to override dependencies levels written on package-lock.json and force the use of dtrace-provider@0.8.8.

Thanks,

@jsumners
Copy link
Member

jsumners commented Dec 2, 2019

Please use ldapjs@next.

Resolved by #466.

@jsumners jsumners closed this as completed Dec 2, 2019
@jsumners
Copy link
Member

⚠️ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.

Please include a minimal reproducible example
when opening a new issue.

@ldapjs ldapjs locked as resolved and limited conversation to collaborators Mar 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants