@logtape/windows-eventlog 1.4.0-dev.466 → 2.0.0-dev.469

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +11 -7
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -10,10 +10,10 @@ Windows Event Log sink for [LogTape]. This package provides a Windows Event Log
10
10
  sink that sends log messages directly to the Windows Event Log system with
11
11
  cross-runtime support and optimal performance.
12
12
 
13
- [JSR]: https://jsr.io/@logtape/windows-eventlog
14
13
  [JSR badge]: https://jsr.io/badges/@logtape/windows-eventlog
15
- [npm]: https://www.npmjs.com/package/@logtape/windows-eventlog
14
+ [JSR]: https://jsr.io/@logtape/windows-eventlog
16
15
  [npm badge]: https://img.shields.io/npm/v/@logtape/windows-eventlog?logo=npm
16
+ [npm]: https://www.npmjs.com/package/@logtape/windows-eventlog
17
17
  [LogTape]: https://logtape.org/
18
18
 
19
19
 
@@ -102,8 +102,9 @@ await configure({
102
102
 
103
103
  > [!NOTE]
104
104
  > The event ID is used to lookup a string resource from a dynamic link library.
105
- > If you do not register a library, “the system cannot open the file” will be
106
- > printed as description in the Event Log regardless of the parameters passed.
105
+ > If you do not register a library, “the system cannot open the file” will
106
+ > be printed as description in the Event Log regardless of the parameters
107
+ > passed.
107
108
 
108
109
  If you want to log only the text supplied by the formatter into the event log,
109
110
  you can register the system generic string library using this command:
@@ -146,11 +147,14 @@ The Windows Event Log sink works across multiple JavaScript runtimes on Windows:
146
147
  Viewing logs
147
148
  ------------
148
149
 
149
- Once your application writes to the Windows Event Log, you can view the logs using:
150
+ Once your application writes to the Windows Event Log, you can view the logs
151
+ using:
150
152
 
151
153
  - *Event Viewer* (*eventvwr.msc*)
152
- - *PowerShell*: `Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='MyApplication'}`
153
- - *Command Prompt*: `wevtutil qe Application /f:text /q:"*[System[Provider[@Name='MyApplication']]]"`
154
+ - *PowerShell*:
155
+ `Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='MyApplication'}`
156
+ - *Command Prompt*:
157
+ `wevtutil qe Application /f:text /q:"*[System[Provider[@Name='MyApplication']]]"`
154
158
 
155
159
 
156
160
  Docs
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@logtape/windows-eventlog",
3
- "version": "1.4.0-dev.466+6520471a",
3
+ "version": "2.0.0-dev.469+3c6fc1d7",
4
4
  "description": "Windows Event Log sink for LogTape",
5
5
  "license": "MIT",
6
6
  "keywords": [
@@ -57,7 +57,7 @@
57
57
  "dist/"
58
58
  ],
59
59
  "peerDependencies": {
60
- "@logtape/logtape": "^1.4.0-dev.466+6520471a"
60
+ "@logtape/logtape": "^2.0.0-dev.469+3c6fc1d7"
61
61
  },
62
62
  "dependencies": {
63
63
  "koffi": "^2.10.0"