- What does the publiux/laravelcdn package do?
- publiux/laravelcdn is a Laravel CDN assets manager. It integrates CDN asset delivery into a Laravel application by letting you configure a provider, upload or push static assets, and generate CDN URLs so images, CSS, and JavaScript are served from the edge instead of your origin. It is installed through Composer and is coupled to illuminate/* versions, so it follows Laravel's major release cadence.
- How do I install publiux/laravelcdn in a Laravel 10 application?
- Install it with Composer and confirm the resolved version is v4.1.0 or later, since that is the release that adds Laravel 10 support. Your host application must already be on PHP 8.1 or newer because that is a Laravel 10 requirement rather than a package requirement. Follow the repository README for any provider configuration or publish steps after installation.
- Does laravelcdn v4.1.0 support Laravel 10, and does it still support Laravel 8 and 9?
- v4.1.0 explicitly adds Laravel 10 support as a minor release on top of 4.0.x. The release notes do not state whether older Laravel versions were dropped or where the new minimum sits. Check the composer.json illuminate/* constraint before upgrading: a widened constraint such as ^9|^10 is safe, while a replaced constraint means the supported floor moved.
- What PHP version do I need to run laravelcdn v4.1.0 on Laravel 10?
- You need PHP 8.1 or newer when using v4.1.0 on Laravel 10, because that is the framework's own requirement. The package notes do not publish a separate PHP floor, so the practical gate is your Laravel version. Teams still on PHP 8.0 cannot adopt this release on Laravel 10 even if their Laravel code is otherwise ready.
- How do I configure a CDN provider with laravelcdn?
- Configuration is provider-driven: you select your CDN provider and supply the credentials, paths, and options that provider needs, and the package uses that configuration when uploading assets and building URLs. The available overview does not document specific config keys, so rely on the repository README for the exact configuration file and options. Validate the setup in a non-production environment before switching production traffic to the CDN.
- How do I upload or push static assets to the CDN using this package?
- The package supports uploading or pushing static assets to your configured CDN, which is a separate concern from generating CDN URLs at render time. A typical flow is to build your front-end assets, push the built asset directories through the package, and then reference them through the package's URL generation. Confirm your build pipeline publishes assets before the URL generation step runs, otherwise you will serve links to files that were never uploaded.
- Can laravelcdn generate CDN URLs for images, CSS, and JavaScript?
- Yes. Generating CDN URLs so images, CSS, and JavaScript load from the edge is the package's core purpose. Once your provider is configured and your assets are pushed, the package produces CDN-hosted URLs that your views and asset helpers can reference. Verify that the configured paths match your actual asset layout, especially if you use versioned or hashed build output.
- Is upgrading from 4.0.x to v4.1.0 a breaking change?
- By semver, no: 4.0.x to 4.1.0 is a minor bump and should be an additive compatibility change that leaves the public API stable. The real risk is that some maintainers raise the minimum Laravel version when adding support for a new major, which quietly cuts off users on older frameworks. Diff composer.json between the tags before merging and keep a rollback point ready.
- Does laravelcdn have a published support or end-of-life policy for future Laravel versions?
- The material available does not state a support or EOL policy, and there is no indication of whether a v5 is planned to coincide with Laravel 11. Without a stated policy, assume only the latest minor receives Laravel compatibility updates. Plan a dependency review each Laravel major and expect some lag, since v4.1.0 arrived after Laravel 10 rather than alongside it.
- What should I check in composer.json before upgrading laravelcdn, and are there alternatives to consider?
- Check the illuminate/* constraint diff first to see whether the range widened or the floor moved, then confirm the package's test matrix actually covers Laravel 10 rather than asserting support without CI. Scan for transitive conflicts, especially packages pinned to illuminate/support ^9, and check whether any behavioral fixes are bundled with the compatibility work. If you need a different feature set or a stricter support policy, compare alternatives before committing.