Upgrading @appium/base-plugin from 3.x to 4.x

Comparison of the public API of @appium/base-plugin 3.3.7 and 4.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths	0
Removed exports	1
Changed signatures	0
Removed class or interface members	1
Changed class or interface members	1
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	0

Removed exports

import	export	kind	Before
`@appium/base-plugin`	`default`	class	`class`

Changed signatures

None detected.

Removed class or interface members

member	import	Before
`BasePlugin.logger`	`@appium/base-plugin`	`AppiumLogger`

Changed class or interface members

member	Before	After
`BasePlugin.cliArgs`	`Record<string, unknown>`	`Readonly<Record<string, unknown>>`

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

	Before	After
`engines.node`	`^20.19.0 \|\| ^22.12.0 \|\| >=24.0.0`	`^22.22.2 \|\| ^24.15.0 \|\| >=26.0.0`

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to Cursor Add to VS Code ★ Star on GitHub

Any other MCP client

{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

Frequently asked questions

What are the breaking changes when upgrading @appium/base-plugin from 3 to 4?

Between @appium/base-plugin 3.3.7 and 4.0.0, Vigia found 1 removed exports, 0 changed signatures and 2 removed or changed class or interface members.

What became deprecated in @appium/base-plugin 4?

0 exports or members are newly marked as deprecated in @appium/base-plugin 4.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/@appium/base-plugin/upgrade?from=3.3.7&to=4.0.0