- How do I install asmit/resized-column in a Laravel Filament application?
- Install it with Composer, register the Filament plugin or service provider, publish its front-end assets, and enable resizing on selected table columns. Because licensing is unresolved and release metadata looks unusual, do the install in a sandbox branch first and pin the exact version. Confirm that asset publishing works in your CI/CD pipeline before deploying.
- Which Filament, Laravel, PHP, Livewire, and Alpine versions are supported?
- The available documentation does not state exact version constraints, so check the package composer.json and release history before installing. Pin your Filament major version and test against the Livewire, Alpine, and Tailwind versions already in your app. Filament table behavior is sensitive to front-end upgrades, so build a small compatibility matrix rather than assuming broad support.
- What license does asmit/resized-column use, and can I use it in production?
- The repository license is reported as NOASSERTION, which means the actual terms are unclear and should be treated as a legal blocker for production use. Do not assume it is MIT or otherwise permissive. Ask the maintainer for written clarification or restrict the package to an internal prototype until the license is resolved.
- Does it work with all Filament column types, including badges, toggles, custom views, and relationship columns?
- That is not documented, and the answer depends on whether the package extends the public Filament column API or patches vendor views and assets. Public-API extension is safer; monkey-patching internals is a real upgrade risk. Test the specific column types used in your tables, especially custom views and responsive layouts, before rolling it out.
- Are column widths persisted per user, per table, or only for the browser session?
- The persistence model is not specified in the available context. Review the source to see whether widths are stored in localStorage, the browser session, a user preference table, or not at all. If persistence is missing, you may need to add your own storage layer or accept session-only behavior.
- Is asmit/resized-column production-ready?
- It has low market validation, with roughly 57 stars and zero dependents, plus single-maintainer and sparse-release risk. A future-dated release anomaly should also be verified before trusting release metadata. Treat it as an optional UI enhancement, pilot it behind a feature flag on one non-critical Filament resource, and keep a rollback path.
- Does the package require an npm build step, or does it ship prebuilt assets?
- This is not clear from the provided information, so confirm whether the Composer package includes compiled JavaScript and CSS or expects you to build assets yourself. Check that published assets work in production and in CI/CD. Also inspect for inline scripts that could conflict with a strict Content Security Policy.
- How does it behave when Livewire re-renders a Filament table?
- Table-column resize features can lose state or misalign when Livewire re-renders, especially if widths are only held in the DOM. Test sorting, filtering, pagination, and search interactions after resizing. If the package does not reconcile widths after re-render, you may need custom JavaScript or a fork to fix it.
- Is there test coverage, CI, and a documented upgrade path?
- The available assessment does not confirm test coverage, CI, or a documented upgrade path, so assume you will own manual QA. Pin the package version and avoid auto-updating it in production. For Filament major upgrades, plan to review the source or fork the package if the maintainer is inactive.
- Does asmit/resized-column resize uploaded images or Filament table columns?
- The package overview and technical assessment describe a Filament table column resize plugin, while the short blurb mentions an image-resizing cast. Those are different features, so verify the actual source before choosing it for either use case. If you need image resizing, confirm that functionality exists and is documented rather than relying on the blurb.