Gathering detailed insights and metrics for @rpai/wdio-logger
Gathering detailed insights and metrics for @rpai/wdio-logger
npm install @rpai/wdio-logger
Typescript
Module System
Node Version
NPM Version
70.2
Supply Chain
89.9
Quality
78.3
Maintenance
100
Vulnerability
100
License
TypeScript (94.41%)
JavaScript (3.33%)
EJS (1.47%)
CSS (0.69%)
Gherkin (0.06%)
Dockerfile (0.03%)
Vue (0.01%)
Total Downloads
484
Last Day
5
Last Week
15
Last Month
30
Last Year
484
9,158 Stars
7,766 Commits
2,530 Forks
216 Watching
26 Branches
614 Contributors
Minified
Minified + Gzipped
Latest Version
1.0.3
Package Id
@rpai/wdio-logger@1.0.3
Unpacked Size
32.15 kB
Size
8.89 kB
File Count
14
NPM Version
10.7.0
Node Version
20.15.0
Publised On
27 Sept 2024
Cumulative downloads
Total Downloads
Last day
66.7%
5
Compared to previous day
Last week
275%
15
Compared to previous week
Last month
328.6%
30
Compared to previous month
Last year
0%
484
Compared to previous year
4
A helper utility for logging of WebdriverIO packages
This package is used across all WebdriverIO packages to log information using the loglevel
package. It can also be used for any other arbitrary Node.js project.
To install the package just call
1npm install @wdio/logger
or when adding it to a WebdriverIO subpackage:
1lerna add @wdio/logger --scope <subpackage>
The package exposes a logger function that you can use to register an instance for your scoped package:
1import logger from '@wdio/logger' 2 3const log = logger('myPackage') 4log.info('some logs')
For more info see loglevel
package on NPM.
This package extends the log levels available in loglevel
by introducing a new level called progress
.
The progress
level is particularly useful when you need to dynamically update a specific line in the terminal. For example, it can be utilized to display the download progress of browsers or drivers.
Notably, the progress
level is equivalent to the info
level. Therefore, if you set the log level to error
or silent
, any progress
logs will be suppressed.
It's important to mention that progress
writes directly to process.stdout
, and these logs won't be captured in any log files.
To ensure consistent formatting with subsequent logs while using progress
, it's essential to clear it at the end. To do so, simply call progress
with an empty string, which will clear the last line:
log.progress('')
1import logger from '@wdio/logger'; 2 3const log = logger('internal'); 4 5const totalSize = 100; 6let uploadedSize = 0; 7 8const uploadInterval = setInterval(() => { 9 const chunkSize = 10; 10 uploadedSize += chunkSize; 11 const data = `Progress: ${(uploadedSize * 100) / totalSize}%`; 12 log.progress(data); 13 if (uploadedSize >= totalSize) { 14 clearInterval(uploadInterval); 15 log.progress(''); // Called at the end to maintain the alignment of subsequent logs. 16 console.log('Upload complete.'); 17 } 18}, 100);
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
Reason
security policy file detected
Details
Reason
license file detected
Details
Reason
binaries present in source code
Details
Reason
badge detected: Passing
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
Found 4/30 approved changesets -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
15 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-01-13
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More