johnpapa / johnpapa/lite-server
{ "logLevel": "warn" } should not print browser-sync configuration on start.
- Dominant language
- JavaScript
- Stars
- 2.3k
- Forks
- 262
- PR merge metrics
- No merged PRs in 30d
Description
Apologies in advance, I have a hunch this should be in browser-sync repo but I'm running via lite-server so I wanted to start here. Also this is obviously a really low priority - just unpleasantly tickling my sensories.
### Issue details
`{ "logLevel": "warn" }` should not print browser-sync configuration on start.
The configuration data should not meet or exceed the log threshold of "warn" - IMO it belongs at "debug"
### Steps to reproduce/test case
file: lite-server.js
```
module.exports = {
"logLevel": "warn"
...
}
```
run command
`>> lite-server --config lite-server.js`
output (current)
```
** browser-sync config **
{ ... big json config block ... }
Access URLs:
-----------------------------------------------
Local: http://localhost:8080/connect/
External: http://192.168.2.128:8080/connect/
-----------------------------------------------
UI: http://localhost:8081
UI External: http://192.168.2.128:8081
```
output (expected)
```
** browser-sync config **
Access URLs:
-----------------------------------------------
Local: http://localhost:8080/connect/
External: http://192.168.2.128:8080/connect/
-----------------------------------------------
UI: http://localhost:8081
UI External: http://192.168.2.128:8081
```
The configuration data should not meet or exceed the log threshold of "warn" - IMO it belongs at "debug"
A log threshold of "silent" produces the the expected output but obviously doesn't log server errors or warnings.
### Version
- lite-server [2.3.0]
- Browsersync [ 2.18.8 ]
- Node [6.10.2]
### Affected platforms
- [ ] linux
- [X] windows
- [ ] OS X
- [ ] freebsd
- [ ] solaris
- [ ] other _(please specify which)_
### Browsersync use-case
- [ ] API
- [ ] Gulp
- [ ] Grunt
- [X] CLI
### If CLI, please paste the entire command below
`lite-server --config lite-server.js`
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.