- How do I install georgebuilds/livewire-molecule in a Laravel app?
- Install it with Composer using composer require georgebuilds/livewire-molecule. It is a standard Laravel/Livewire component, so no new services, daemons, or infrastructure are required. No config publish or migration step is announced for the 2.1.0 release, but check the repository README for the current install instructions. Before running a routine composer update, confirm that your laravel/framework and livewire/livewire constraints intersect with the package's own constraints.
- What Laravel and Livewire versions does livewire-molecule support?
- The 2.1.0 support matrix targets Laravel 11, 12, and 13, with Laravel 11 unconfirmed and Laravel 13 possibly provisional if that framework line is not yet GA. On the Livewire side, version 2.1.0 drops Livewire 3 without stating an explicit replacement, so Livewire 4 support is inferred rather than documented. Read the tagged release's composer.json to confirm the exact constraints instead of relying on release notes alone.
- Does livewire-molecule work with Laravel 10 or Livewire 3?
- No. Version 2.1.0 drops both Laravel 10 and Livewire 3, and that support-matrix break was shipped in a minor release rather than a major one. If your application is still on Laravel 10 or Livewire 3, pin to ^2.0.0 or the exact 2.0.x version you validated before any composer update runs. Pinning defers the problem rather than solving it, and the usable life of the 2.0.x line depends on the maintainer's backport policy.
- Why did upgrading livewire-molecule to 2.1.0 break my composer update?
- Dropping two framework majors in a minor release means a floating ^2.0 constraint can no longer resolve on a Laravel 10 host, so Composer fails at install time rather than at runtime. The immediate fix is to pin an exact 2.0.x release you have already validated until your framework upgrade lands. Treat the failure as a signal to schedule the move to Laravel 11 or newer rather than as an isolated package bug.
- How do I render a 3D molecule inside a Livewire component?
- The package wraps 3DMol.js in a Livewire component for 3D molecular visualization, so you render it from Blade like any other Livewire component while keeping your markup declarative. Exact property names, data binding, and molecule input formats should be taken from the README of the version you install, since the excerpt available here is empty. Because 3DMol.js runs in the browser, make sure its JavaScript asset is loaded on any page that displays a molecule.
- Do I need to publish a config file or run migrations after installing livewire-molecule?
- The 2.1.0 release announces no config publish step and no migrations, which helps keep integration effort low. If a publishable config exists, it should be documented in the repository README for your installed version. Verify against the package's service provider rather than assuming defaults, especially if you are upgrading from a 2.0.x release.
- Does livewire-molecule ship test helpers, and are they safe to keep in production?
- The release notes mention adding test methods for local development but do not say whether those helpers are included in the distributed package or excluded from autoloading and service-provider registration in production. Until that is clarified, check composer.json autoload-dev entries and any environment conditionals in the service provider. If you rely on them in CI, ask the maintainer to confirm the supported testing API for the version you pinned.
- What PHP version does livewire-molecule require?
- The PHP floor is not stated in the available release information and should be read directly from composer.json in the tagged release rather than inferred. Since Laravel 11 and 12 themselves require PHP 8.2 or newer, that is the likely baseline, but confirm it before upgrading legacy applications. Do not assume the package's PHP constraint matches the framework's exactly.
- Is Laravel 13 support in livewire-molecule stable or pre-release?
- Version 2.1.0 adds Laravel 13 to the supported matrix, but if that framework line is not GA at the time of the tag, the support is provisional and may churn. Supporting a framework that is not yet your deployment baseline adds little near-term value and can create a false impression of readiness. Keep your production baseline on Laravel 12 until 13 is GA and the maintainer states a policy for pre-GA support.
- Is livewire-molecule actively maintained, and what are the alternatives?
- Release 2.1.0 shows active maintenance, but a support-matrix break published as a minor version means you should read release notes carefully on every update and pin versions you have validated. Alternatives include integrating 3DMol.js directly with Blade and Alpine, or using other chemistry viewers, if you want to avoid package-level coupling to framework majors. For teams already on Laravel 11 or newer and the current Livewire line, the wrapper saves considerable boilerplate.