npm upgrade
Hometestcontainers 9 → 10
9.12.0 → 10.28.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
testcontainers 10.28.0 removes or renames exports your code may import.
- Removed
- 26
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 16
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade testcontainers@9.12.0..10.28.0
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- AlwaysPullPolicyobject
- ArangoDBContainerobject
- DefaultPullPolicyobject
- ElasticsearchContainerobject
- HiveMQContainerobject
- KafkaContainerobject
- MongoDBContainerobject
- MySqlContainerobject
- NatsContainerobject
- Neo4jContainerobject
- PostgreSqlContainerobject
- SeleniumContainerobject
- SeleniumRecordingContainerobject
- StartedArangoContainerobject
- StartedElasticsearchContainerobject
- StartedHiveMQContainerobject
- StartedKafkaContainerobject
- StartedMongoDBContainerobject
- StartedMySqlContainerobject
- StartedNatsContainerobject
- StartedNeo4jContainerobject
- StartedPostgreSqlContainerobject
- StartedSeleniumContainerobject
- StartedSeleniumRecordingContainerobject
- StoppedSeleniumContainerobject
- StoppedSeleniumRecordingContainerobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 11, 2026. testcontainers on lurq.