Doesn't work when installed as a package dependency

[cecilia-sanare]

When adding dns-proxy as a package dependency and trying to run it using a npm script.

  // ...
  "scripts": {
    "start": "dns-proxy"
  },
  "dependencies": {
    "dns-proxy": "*"
    // ...
  }
  // ...

It will try to load ../dns-proxy.js which doesn't exist relative to the bin that node runs.

Workaround

  // ...
  "scripts": {
    "start": "node node_modules/dns-proxy"
  }
  // ...

[ekristen]

Thanks to email alerts I totally missed these details when i was looking at this from my phone, sorry about that. I'll admit I never planned on this being used as a dependency. Let me take a look at the PR.

Off the top of my head you could always do this now and have it work node node_modules/dns-proxy/dns-proxy.js

[cecilia-sanare]

That's actually what my workaround does except node reads the main property in the package.json on our behalf.

Also you've definitely created a rockstar module. This is so simple to setup compared to the alternatives.

[ekristen]

Thanks for the kind words, glad it works for you. I'm working on an update that will dynamically read in changes from the conf file.

…

Sent from my iPhone

On Jan 29, 2017, at 08:56, Nick Woodward ***@***.***> wrote: That's actually what my workaround does except node reads the main property in the package.json on our behalf. Also you've definitely created a rockstar module. This is so simple to setup compared to the alternatives. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.