- How do I install arielmejiadev/larapex-charts in a Laravel application?
- Install it with Composer using composer require arielmejiadev/larapex-charts. Laravel package auto-discovery normally registers the service provider, so most applications need no manual provider entry, but confirm any config or asset publishing steps in the repository README. Version 10.0.0 is the release that adds Laravel 13 support, so match the package major to your framework version.
- Which Laravel versions does larapex-charts support?
- The only evidence available is the 10.0.0 release note, which states 'support laravel 13'. Earlier majors targeted older Laravel releases, but no full compatibility matrix is published in that note. Read the illuminate constraint in composer.json to confirm exactly which Laravel versions 10.x accepts.
- Do I need to write JavaScript to use Larapex Charts?
- No, you define charts in PHP or Blade with fluent methods and the package assembles the ApexCharts configuration for you. The charts still render in the browser through the ApexCharts JavaScript library, which provides the interactivity and responsiveness. You are avoiding hand-written chart config, not the client-side library itself.
- What chart types can I build with larapex-charts?
- The package supports line, bar, pie, donut and radial charts, among others. Each type is created through the same fluent PHP API, so switching chart types is largely a matter of changing the builder method. Labels, colors, data series and other options are customizable.
- Is version 10.0.0 a breaking change from 9.x?
- It is a semver major, so treat it as breaking until proven otherwise. The release note only mentions Laravel 13 support, and compatibility majors often bundle replaced dependency constraints, PHP version floors or service provider changes that a one-line note does not disclose. Review the composer.json diff and any upgrade guide before bumping.
- Can I still use larapex-charts on Laravel 11 or 12 after upgrading to 10.0.0?
- It depends on whether 10.0.0 replaced the illuminate constraint with Laravel 13 only or widened it to include 11 and 12. If it was replaced, 10.x cannot be installed alongside older Laravel versions and the jump is coupled to a framework upgrade. Check the constraint in composer.json before planning the upgrade.
- How do I upgrade larapex-charts from 9.x to 10.0.0 safely?
- First check whether 10.0.0 changes only the framework constraint or also touches class names, config keys or method signatures. If the constraint was widened, upgrade the package on your current Laravel version first to isolate package regressions from framework regressions. If it was replaced, plan the bump as part of your Laravel 13 upgrade window.
- How should I test charts built with larapex-charts?
- Because rendering happens client-side, feature tests usually assert the fluent API output, such as the generated config array or the Blade markup that carries it, rather than pixels. Add a browser-level test if you need to prove the chart actually renders. Keep dataset fixtures small so assertions stay readable.
- Does larapex-charts add server-side performance overhead in production?
- The PHP side mostly builds a configuration payload, so cost is small relative to rendering, which ApexCharts performs in the browser. Watch dataset size, because very large series are serialized into the page and can slow both the response and the client. Aggregating or paginating data server-side keeps charts responsive.
- Is larapex-charts actively maintained, and what are the alternatives?
- A release that tracks a new Laravel major is a positive sustainability signal, because it shows the maintainer follows framework cadence. However, a one-line release note suggests limited documentation effort, and maintainer count and bus factor are not visible from the note alone. Alternatives include other Laravel chart wrappers or using ApexCharts directly from Blade with your own JSON payload.