-
Notifications
You must be signed in to change notification settings - Fork 2
Package Switch and Migration
ImperaZim edited this page Jun 21, 2026
·
1 revision
Use this flow when replacing a standalone library with an EasyLibrary package.
- Install the package while the standalone is still present.
/easylibrary packages install libplaceholder stable confirm
restart server
- Confirm the package is shadowed by standalone.
/easylibrary packages doctor
- Run the switch checklist.
/easylibrary packages switch libplaceholder
/easylibrary packages switch libplaceholder confirm
- Stop the server.
- Move the standalone PHAR or folder out of
plugins/. - Start the server.
- Validate.
/pl
/easylibrary packages doctor
/easylibrary doctor
Development-only probe:
/elprobe run libplaceholder
- Park or remove the package proxy.
- Stop the server.
- Add the standalone PHAR.
- Start the server.
- Confirm standalone wins.
/easylibrary packages switch libplaceholder park
restart server
/easylibrary packages doctor
Switch one provider at a time. This keeps problems small and rollback obvious.
- Package Manager
- Package Backed Plugins
- Standalone vs Package
- Package Switch and Migration
- Package Doctor
- Package Safety Gate
- Support Report Bundle
- Timings
- Package Recovery
- Proxy Troubleshooting
- Migrating from EasyLibrary 2.0 to 3.x
- Embedded Libraries Migration Map
- Removed Features and Replacements
- Deprecated APIs
- Compatibility Policy
- Config Migration
- 3x Dev Scope Checkpoint
- Plugin Developer Migration
- Server Administrator Migration
- Official Libraries
- LibPacket
- LibCommand
- LibSerializer
- LibForm
- LibDB
- LibCommons
- LibHttp
- LibAssets
- LibPlaceholder
- LibWorld
- EasyLibrary Agent Bridge
- LibCustom
- LibEnchantment
- LibHud
- LibTrigger
- LibWindow
- Public API Contract
- Module Boundary
- Module Smoke Matrix
- LibAsync Incubator
- LibReflect Incubator
- Doctor Output
- Repository Notifications
- Smoke Tests
- Common Errors
- Release and Changelog