taila
Advanced tools
Comparing version 1.0.3 to 1.1.0-rc1
{ | ||
"name": "taila", | ||
"version": "1.0.3", | ||
"description": "This is a utility for tailing a text file similar to tail -f but with a few extra features", | ||
"version": "1.1.0-rc1", | ||
"description": "", | ||
"main": "src/tail.js", | ||
@@ -9,10 +9,6 @@ "scripts": { | ||
}, | ||
"author": "Knut Sveidqvist", | ||
"license": "MIT", | ||
"repository": { | ||
"type": "git", | ||
"url": "https://github.com/knsv/taila.git" | ||
}, | ||
"author": "", | ||
"license": "ISC", | ||
"dependencies": { | ||
"@uppy/fs-tail-stream": "^1.2.0", | ||
"@uppy/fs-tail-stream": "^1.2.0", | ||
"byline": "^5.0.0", | ||
@@ -28,4 +24,4 @@ "chalk": "^2.4.2", | ||
"bin": { | ||
"taila": "src/index.js" | ||
"tailor": "src/server.js" | ||
} | ||
} |
@@ -9,13 +9,7 @@ # Tail with pattern matching and filtering | ||
![Animated gif showing command](demo.gif) | ||
] | ||
## Get started | ||
Perform | ||
``` | ||
npm install taila -g | ||
``` | ||
## Basic usage | ||
Usage: taila [options] [filename] | ||
Usage: index [options] [filename] | ||
@@ -29,7 +23,7 @@ Options: | ||
``` | ||
taila server.log | ||
taila -a server.log | ||
tailor server.log | ||
tailor -a server.log | ||
``` | ||
During tailing it is possible to affect the operation of the tail process by pressing some command keys on the keyboard. | ||
During tailoring it is possible to affect the operation of the tail process by pressing some command keys on the keyboard. | ||
@@ -47,68 +41,2 @@ Commands during tailing: | ||
For the command to work properly it needs to have a list of patterns to search for. These patterns are configured in a file named .tailor.conf.js. | ||
The command first looks for the ocnfig file in the current working directory. If that fails it looks in the users home folder for the file. | ||
The file looks like this: | ||
```javascript | ||
module.exports = { | ||
highlights: [ | ||
{ | ||
pattern: "[ERROR]", | ||
re: false, | ||
bkg: "bgRed", | ||
color: "black" | ||
}, | ||
{ | ||
pattern: "DEBUG", | ||
color: "green" | ||
}, | ||
{ | ||
pattern: "INFO", | ||
color: "blue", | ||
} | ||
] | ||
}; | ||
``` | ||
The pattern is either a substring or a regular expression. The property re is a flag indikating oid the pattern string ia regular expression or substring. | ||
The colors have the following possible values: | ||
### Colors | ||
- `black` | ||
- `red` | ||
- `green` | ||
- `yellow` | ||
- `blue` *(On Windows the bright version is used since normal blue is illegible)* | ||
- `magenta` | ||
- `cyan` | ||
- `white` | ||
- `gray` ("bright black") | ||
- `redBright` | ||
- `greenBright` | ||
- `yellowBright` | ||
- `blueBright` | ||
- `magentaBright` | ||
- `cyanBright` | ||
- `whiteBright` | ||
### Background colors | ||
- `bgBlack` | ||
- `bgRed` | ||
- `bgGreen` | ||
- `bgYellow` | ||
- `bgBlue` | ||
- `bgMagenta` | ||
- `bgCyan` | ||
- `bgWhite` | ||
- `bgBlackBright` | ||
- `bgRedBright` | ||
- `bgGreenBright` | ||
- `bgYellowBright` | ||
- `bgBlueBright` | ||
- `bgMagentaBright` | ||
- `bgCyanBright` | ||
- `bgWhiteBright` | ||
For the command to work properly |
SPDX disjunction
LicenseSPDX disjunction for an artifact's license information
Found 1 instance in 1 package
Mixed license
License(Experimental) Package contains multiple licenses.
Found 1 instance in 1 package
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
SPDX disjunction
LicenseSPDX disjunction for an artifact's license information
Found 1 instance in 1 package
605256
2
2
3
39
3