--config does not take absolute path

[xkxx]

Hello,

Currently --config does not take absolute paths. For example, doing something like this throws an error:

> browser-sync start --config /etc/bs-config.js

module.js:318
    throw err;
    ^
Error: Cannot find module '/path/to/cwd/etc/bs-config.js'

This is caused by browser-sync/lib/cli/cli-info.js:28:

        return require(path.resolve(process.cwd() + "/" + filePath));

Which tries to resolve relative url by prepending process.cwd(), but that's the job of path.resolve.
Changing this line to the following does the correct thing, and fixes the issue:

        return require(path.resolve(process.cwd(), filePath));

Thanks,

Kexiang

[shinnn]

Confirmed. Thanks for your detailed reporting, @xkxx.

[shakyShane]

thanks @xkxx - but where is the PR ? :p

[xkxx]

I thought about it, but then thought it was too trivial to be worth a PR - hope I have provided enough info for you guys to fit it :)

[shakyShane]

Nothing is too trivial for a PR :)

[xkxx]

Speaking of trivial PRs, would you mind taking a look at shakyShane/html-injector#5?
It fixes a problem with browser-sync failing when ui is disabled. Travis CI test is failing, but I don't really know about the inner-workings of the module to get what's going on.

[shakyShane]

Ahh yeah I saw that - it's on the list for the next round of bug fixes / pr's :)