@appium/logger upgraden van 2.x naar 3.x
Vergelijking van de publieke API van @appium/logger 2.0.12 en 3.0.0, automatisch berekend uit hun TypeScript-types. Een gewijzigde signatuur is een mogelijke brekende wijziging, geen zekerheid.
Samenvatting
| Verwijderde importpaden | 0 |
|---|---|
| Verwijderde exports | 1 |
| Gewijzigde signaturen | 0 |
| Verwijderde leden van klassen of interfaces | 5 |
| Gewijzigde leden van klassen of interfaces | 1 |
| Nieuw als verouderd gemarkeerd | 0 |
| Gewijzigde vereisten (engines, peer-afhankelijkheden) | 1 |
| Nieuwe exports | 1 |
Verwijderde exports
| import | export | kind | Voor |
|---|---|---|---|
@appium/logger | default | variable | Log |
Gewijzigde signaturen
Niets gevonden.
Verwijderde leden van klassen of interfaces
| member | import | Voor |
|---|---|---|
Logger.enableUnicode | @appium/logger | (): void |
Logger.disableUnicode | @appium/logger | (): void |
Logger.enableProgress | @appium/logger | (): void |
Logger.disableProgress | @appium/logger | (): void |
Logger.progressEnabled | @appium/logger | (): boolean |
Gewijzigde leden van klassen of interfaces
| member | Voor | Na |
|---|---|---|
Logger.log | (level: string, prefix: string, message: any, ...args: any[]): void | (level: CustomLogLevel, prefix: string, message: any, ...args: any[]): void |
Nieuw als verouderd gemarkeerd
Niets gevonden.
Gewijzigde vereisten (engines, peer-afhankelijkheden)
| Voor | Na | |
|---|---|---|
engines.node | ^20.19.0 || ^22.12.0 || >=24.0.0 | ^22.22.2 || ^24.15.0 || >=26.0.0 |
Nieuwe exports (1)
| import | export | kind |
|---|---|---|
@appium/logger | CustomLogLevel | type |
Changelog tussen deze versies
Tekst gepubliceerd door de pakketauteurs, ongewijzigd weergegeven.
3.0.0
### ⚠ BREAKING CHANGES
* **support:** Any script or tool that consumes Appium CLI output (driver/plugin list/install/update, doctor, etc.) and relies on the previous stream layout will need to be updated. Previously, non-JSON human-readable output (info/success/warning messages) was written to STDERR, with STDOUT reserved almost exclusively for --json output. Now that output goes to STDOUT, and only actual errors go to STDERR.
* **support:** Scripts that discarded STDOUT (1>/dev/null) to suppress "chatter" while relying on STDERR for status text will now see that text on STDOUT instead.
* **support:** Scripts that captured STDERR to detect/log informational or success messages will no longer see them there — only genuine errors will appear on STDERR. --json output and error behavior are unaffected: --json continues to write clean JSON to STDOUT only, and errors continue to go to STDERR.
* **support:** @appium/logger's Log class changes its default output stream from STDERR to STDOUT for all levels except error, and adds an errorStream/stderrLevel pair of properties. Any code that set .stream on a Log instance expecting it to capture all levels (including error) will now need to also set .errorStream to the same target.
* **logger:** @appium/logger and @appium/support no longer export a default log — import the named log export instead.
* **logger:** AppiumLogger#errorAndThrow has been removed; use errorWithException instead.
* **logger:** Logger#enableProgress, disableProgress, progressEnabled, enableUnicode, disableUnicode have been removed; they were already permanently disabled no-ops.
* the minimum supported Node.js engine is set to ^22.22.2 || ^24.15.0 || >=26.0.0
* require('@appium/support') no longer works; consumers must import it instead.
* require('@appium/base-driver') no longer works; drivers extending BaseDriver via require must switch to import.
* require('@appium/base-plugin') no longer works; plugins extending BasePlugin via require must switch to import.
* require('appium') no longer works; plugins extending the package via require must switch to import.
* require('@appium/fake-plugin') no longer works; consumers must import it instead.
* require('@appium/fake-driver') no longer works; consumers must import it instead.
* require('@appium/types') no longer works; consumers must import it instead.
* require('@appium/logger') no longer works; consumers must import it instead.
* require('@appium/schema') no longer works; consumers must import it instead.
### Features
* bump minimum supported Node.js engine to ^22.22.2 || ^24.15.0 || >=26.0.0 ([#22685](https://github.com/appium/appium/issues/22685)) ([8ad9193](https://github.com/appium/appium/commit/8ad9193115129e8bcae9fff7845dd753431ff687))
* convert remaining monorepo packages to ESM-only ([#22674](https://github.com/appium/appium/issues/22674)) ([48452fe](h3.0.0-beta.2
3.0.0-beta.1
**Note:** Version bump only for package @appium/logger3.0.0-beta.0
### ⚠ BREAKING CHANGES
* **support:** Any script or tool that consumes Appium CLI output (driver/plugin list/install/update, doctor, etc.) and relies on the previous stream layout will need to be updated. Previously, non-JSON human-readable output (info/success/warning messages) was written to STDERR, with STDOUT reserved almost exclusively for --json output. Now that output goes to STDOUT, and only actual errors go to STDERR.
* **support:** Scripts that discarded STDOUT (1>/dev/null) to suppress "chatter" while relying on STDERR for status text will now see that text on STDOUT instead.
* **support:** Scripts that captured STDERR to detect/log informational or success messages will no longer see them there — only genuine errors will appear on STDERR. --json output and error behavior are unaffected: --json continues to write clean JSON to STDOUT only, and errors continue to go to STDERR.
* **support:** @appium/logger's Log class changes its default output stream from STDERR to STDOUT for all levels except error, and adds an errorStream/stderrLevel pair of properties. Any code that set .stream on a Log instance expecting it to capture all levels (including error) will now need to also set .errorStream to the same target.
* **logger:** @appium/logger and @appium/support no longer export a default log — import the named log export instead.
* **logger:** AppiumLogger#errorAndThrow has been removed; use errorWithException instead.
* **logger:** Logger#enableProgress, disableProgress, progressEnabled, enableUnicode, disableUnicode have been removed; they were already permanently disabled no-ops.
* the minimum supported Node.js engine is set to ^22.22.2 || ^24.15.0 || >=26.0.0
* require('@appium/support') no longer works; consumers must import it instead.
* require('@appium/base-driver') no longer works; drivers extending BaseDriver via require must switch to import.
* require('@appium/base-plugin') no longer works; plugins extending BasePlugin via require must switch to import.
* require('appium') no longer works; plugins extending the package via require must switch to import.
* require('@appium/fake-plugin') no longer works; consumers must import it instead.
* require('@appium/fake-driver') no longer works; consumers must import it instead.
* require('@appium/types') no longer works; consumers must import it instead.
* require('@appium/logger') no longer works; consumers must import it instead.
* require('@appium/schema') no longer works; consumers must import it instead.
### Features
* bump minimum supported Node.js engine to ^22.22.2 || ^24.15.0 || >=26.0.0 ([#22685](https://github.com/appium/appium/issues/22685)) ([9f4a11e](https://github.com/appium/appium/commit/9f4a11e7190290986d01743557e90e6e44f87638))
* convert remaining monorepo packages to ESM-only ([#22674](https://github.com/appium/appium/issues/22674)) ([3516e50](hGeef je AI-agent deze feiten
Vigia is een gratis MCP-server: je coding-agent controleert versies, breaking changes en kwetsbaarheden voordat hij code schrijft. Geen account, geen API-sleutel.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Toevoegen aan CursorToevoegen aan VS Code★ Ster op GitHub
Elke andere MCP-client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent-skill (SKILL.md): vertelt de agent wanneer hij Vigia moet gebruiken · GitHub Action voor pull requests
Veelgestelde vragen
Wat zijn de brekende wijzigingen bij het upgraden van @appium/logger van 2 naar 3?
Tussen @appium/logger 2.0.12 en 3.0.0 vond Vigia 1 verwijderde exports, 0 gewijzigde signaturen en 6 verwijderde of gewijzigde leden van klassen of interfaces.
Wat is verouderd in @appium/logger 3?
0 exports of leden zijn in @appium/logger 3.0.0 nieuw als verouderd gemarkeerd.
Voor agents
GET https://vigia.coredls.cloud/v1/packages/npm/@appium/logger/upgrade?from=2.0.12&to=3.0.0