Livewire 3 Upgrade Blocker Lint
Runs the same checker as the npm package
@readystack/livewire3-upgrade-blocker-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
The Livewire 2 lines that die quietly in Livewire 3 — named, with the v3 replacement beside each
Install
livewire3-upgrade-blocker-lint file
Node 18+. The same 15 rules as the VS Code extension, from a terminal or CI.
Free
- Scan the .php or .blade.php file you have open and get every Livewire 3 blocker with its v3 replacement, line by line — no key, no watermark, no run limit.
--ruleslists every rule
With a licence ($29 once)
- Scan every .php and .blade.php in the workspace in one command and export an owned REPORT.md / JSON with file:line for the whole migration, plus a non-zero exit code for CI.
@readystack/livewire3-upgrade-blocker-lint --dir ./templates --report html --out report.html
A freelance Laravel developer at $85/hour spends the opening hours of an upgrade making this inventory by hand
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "livewire3-upgrade-blocker-lint": { "command": "npx", "args": ["-y", "@readystack/livewire3-upgrade-blocker-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Livewire 3 Upgrade Blocker Lint
run: npx -y @readystack/livewire3-upgrade-blocker-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/livewire3-upgrade-blocker-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-livewire3-upgrade-blocker-lint
livewire3-upgrade-blocker-lint --help
Metadata
Release files for readystack-livewire3-upgrade-blocker-lint 1.0.6.post1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_livewire3_upgrade_blocker_lint-1.0.6.post1.tar.gz | 15.5 kB | Without provenance | Details for readystack_livewire3_upgrade_blocker_lint-1.0.6.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_livewire3_upgrade_blocker_lint-1.0.6.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_livewire3_upgrade_blocker_lint-1.0.6.post1-py3-none-any.whl |
Total release size: 33.4 kB
Release files / readystack_livewire3_upgrade_blocker_lint-1.0.6.post1.tar.gz
| Download URL | readystack_livewire3_upgrade_blocker_lint-1.0.6.post1.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1c1f1627ae6c8c347d89934f9e753ea2a59f5631ac691651a5229b7c39f2ea0
|
|
BLAKE2b-256 checksum How to use checksums |
4c20564fbbd5cbff7f2ce8d6738e17ee2be4ad6205a2da7fb28972753b72fcc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_livewire3_upgrade_blocker_lint-1.0.6.post1-py3-none-any.whl
| Download URL | readystack_livewire3_upgrade_blocker_lint-1.0.6.post1-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3c9f6f82d27fec9180fb4bd682072c24fdd700946e2ed4f1b0405dd0e8504ec
|
|
BLAKE2b-256 checksum How to use checksums |
26ae8cacc8e6928851eaf77afa75e8c2177307b2d6733b8fcaea7d3d8fd8ac1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-livewire3-upgrade-blocker-lint 1.0.6.post1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.