- How do I install smorken/components in a Laravel application?
- Install it with Composer, but note that the package is hosted on Bitbucket rather than Packagist. You will need to add a repositories entry of type vcs pointing at https://bitbucket.org/scott_morken/components.git in your composer.json, then require the package. Because Bitbucket access may be required, wire credentials into CI and developer machines before rollout. After install, check whether the service provider is auto-discovered or must be registered manually in config/app.php.
- Is smorken/components available on Packagist?
- There is no Packagist presence implied by the package metadata, so you cannot simply run composer require smorken/components. Consumption requires a VCS repository entry plus Bitbucket credentials. Mirroring the repository internally is the recommended way to remove that friction from every environment. Without Packagist, you also lose semver guarantees and Packagist metadata surfaces such as download counts and advisory coverage.
- Which Laravel versions does smorken/components support?
- The supported Laravel and PHP matrix is not verified in the available metadata, so confirm the illuminate/support constraints in the package composer.json before committing. Laravel 7 introduced native class-based and anonymous Blade components with slots and attribute bags, which overlaps heavily with what this package provides. If your application is on Laravel 8 or later, the built-in component system may already cover the same use case without an extra dependency.
- What Blade components does smorken/components actually provide?
- The package describes a convention-based set of reusable Blade components for common UI elements such as buttons, cards, alerts and form fields. Do a source review of resources/views to confirm exactly which components ship before assuming a specific one exists. You should also check whether it includes any JavaScript or CSS assets, since those would need reconciling with your Vite pipeline.
- Do I need to publish the views to customize the components?
- The package advertises publishable views, which means you can run php artisan vendor:publish to copy the Blade files into your own resources/views directory for full customization. Publishing gives you complete control but also means upgrades will not automatically propagate changes to the published copies. If you only need minor tweaks, consider wrapping the vendor components in your own components instead of publishing everything.
- Does smorken/components support slots and attribute passthrough?
- Yes, the package advertises attribute and slot support for flexible, composable markup, which is the standard Blade component mechanism. That means you can pass named slots and arbitrary HTML attributes through to the rendered element. Verify the specifics in the component source, since attribute bag handling differs between class-based and anonymous components.
- Does smorken/components ship CSS or JS assets that conflict with Vite?
- This is unconfirmed from the metadata and should be the first thing you check in a source review. If the package ships stylesheets or scripts, you must either import them into your Vite build or serve them statically, and that reconciliation is the most likely source of integration friction. A Blade-only package with no front-end assets avoids the problem entirely.
- Is smorken/components safe to use in production?
- Treat it as unproven: it is a single-maintainer Bitbucket repository with no stars, no known dependents and no Packagist footprint, so there is no evidence it has run in another team's production. Because it is a VCS dependency, composer audit and Packagist advisory coverage will not protect you. The blast radius is limited to your view layer, but the bus factor risk of a repo rename or credential rotation breaking composer install across every environment is real.
- How do I test Blade components from smorken/components?
- It is not confirmed whether the package ships its own test suite or CI configuration, so check for a phpunit.xml and a tests directory before relying on it. In your own application you can render the components in feature tests using $this->view() or Blade::render() and assert on the resulting HTML. If the package has no tests, adding a small smoke test that renders each component is a cheap way to catch breakage on Laravel upgrades.
- What are the alternatives to smorken/components for reusable Blade components?
- Laravel's native class-based and anonymous Blade components, available since Laravel 7, cover slots and attribute bags with no extra dependency. If you want a larger prebuilt library, packages such as Blade UI Kit or Laravel Blade Components offer maintained, Packagist-hosted collections. For a small internal set of buttons and form fields, writing your own components in resources/views/components is usually less risk than adopting an unmaintained VCS dependency.