- What does goellner/table-on-steroids actually do?
- It is a Statamic 3 add-on that adds a CSV parser to the table fieldtype, so content editors can bring CSV data into a table field inside the control panel. It is not a general-purpose Laravel CSV ingestion library, and it does not add sorting, filtering, or generic data table features to arbitrary Laravel applications. Treat it as a narrow editorial convenience for Statamic projects that already use table fields.
- Do I need Statamic to use this package, or does it work in any Laravel app?
- You need Statamic 3. The package hooks into the Statamic table fieldtype and its control panel asset pipeline, so it has no meaningful behaviour in a plain Laravel app, a headless Laravel API, or an automated ingestion pipeline. If you only need CSV parsing in Laravel, write a small importer or use a dedicated CSV library instead.
- Which Statamic and PHP versions does table-on-steroids support?
- The repository targets Statamic 3, and the exact PHP constraint should be confirmed in the package's composer.json before installing. There is no evidence of tested support for Statamic 4 or 5, so do not assume compatibility after a CMS upgrade. Check the Composer constraints, addon auto-discovery, and any frontend asset build requirements against your target versions.
- How do I install goellner/table-on-steroids?
- Install it with Composer in a non-production branch and pin the exact version you validate. Statamic addons are typically auto-discovered, but confirm registration and that the control panel assets load correctly. Then test the parser against the specific table field handle and Blueprint configuration you plan to use.
- Is table-on-steroids compatible with Statamic 4 or 5?
- Compatibility is not established, and the addon likely depends on Statamic 3 fieldtype internals and frontend assets that may have changed. If you are on Statamic 4 or 5, or planning an upgrade, do not install it on the assumption that it works. Either fork and upgrade the addon yourself or replace it with a small custom importer or fieldtype extension.
- How does it handle CSV edge cases like quoted commas, delimiters, and encodings?
- The repository does not document its parsing behaviour in detail, so you must verify it with representative files. Test quoted commas and newlines, alternative delimiters, UTF-8 and legacy encodings, inconsistent column counts, and malformed rows. Also confirm whether parsing happens client-side or server-side and whether it validates column counts or sanitises values before writing to the table field.
- Is it safe to use table-on-steroids in production?
- Treat it as self-supported: it has zero stars, zero dependents, and no visible evidence of security review or test coverage. CSV imports also introduce risks such as spreadsheet formula injection, silent truncation, and field data corruption. Require validation and previews, take backups, restrict who can import, and keep a documented rollback path before production use.
- Can it handle large CSV files or automated bulk imports?
- It is intended for small, manual editorial imports into table fields, not scheduled ingestion or high-volume pipelines. Large files risk browser performance problems if parsing is client-side, or memory and timeout limits if it is server-side. For bulk or recurring imports, build a job-based Artisan importer with explicit memory, time, and validation controls instead.
- How should I test table-on-steroids before giving it to editors?
- Spike it in a branch with real content and a representative set of CSV files, including deliberately malformed ones. Verify the stored data shape after import, check permissions and asset loading, and confirm the table field still behaves correctly in the control panel. Then pilot with a small editor group and document both the editorial workflow and the rollback steps.
- What are my alternatives if the package is abandoned or breaks on upgrade?
- The fallback is a small custom importer or Artisan command that parses CSV and writes into the table field's stored structure, or a custom fieldtype extension if editors need the in-panel experience. Because there is no ecosystem support, plan to vendor or fork the addon and confirm the licence permits internal modification. Pin the version now and review it whenever you upgrade Statamic.