-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
web-ext commands fail on dynamic linking (OS X) (node-dtrace-provider, bunyan) #1405
Comments
Thanks for the bug report and sorry you had trouble installing web-ext. This looks bad. Various dtrace errors have plagued us in the past but they've always been non-fatal warnings, unlike now. The dtrace bindings are for an obscure feature of our We should consider ditching Here's an example of migrating from |
@hellerve Do you have |
I haven’t revisited this problem since filing this report, but uninstalling Thanks for finding this workaround, @andrewgould! |
I just encountered this with I'm running OSX Mojave |
Is this issue still actual? |
I am not sure, it's old and Node 11 isn't supported anymore. We'll want to get rid of |
Is this a feature request or a bug?
This is a bug, probably caused by a third-party plugin.
What is the current behavior?
I installed web-ext via npm (Node version: v11.4.0) on OS X 10.14.1 today, using
npm install -g web-ext
. Every invocation I’ve used as of yet aborts with the following message:This is apparently caused by a problem in the
node-dtrace-provider
package (see chrisa/node-dtrace-provider#118), which has been open since May and received no activity from the author (who also hasn’t commited to master since then). It thus does not seem as if this issue will get fixed anytime soon, which means that a fallback/workaround might be necessary?What is the expected or desired behavior?
I expect the commands to run without dynamic linking errors.
Version information (for bug reports)
The text was updated successfully, but these errors were encountered: