Weave Code
Nightfall Laravel Package
affandra-solusi-teknologi/nightfall
Nightfall is a Laravel package from Affandra Solusi Teknologi that provides a simple, configurable way to add nighttime-aware behavior to your application, with clean integration and minimal setup for scheduled or after-hours features.
Nightfall is a lightweight Laravel package that brings first-class dark mode support to your application. It handles theme detection, persistence, and switching so you can focus on building UI instead of wiring preference logic. Works with Blade, Tailwind CSS, and your existing auth stack.
- Persist user theme preference via session, cookie, or database
- Blade components and directives for toggling themes
- Automatic system-preference detection with
prefers-color-scheme - Configurable class or data-attribute strategy for Tailwind
- Middleware and helper APIs for server-side theme control
Frequently asked questions about Nightfall
- How do I install affandra-solusi-teknologi/nightfall in a Laravel app?
- Install it with Composer using composer require affandra-solusi-teknologi/nightfall, and pin the exact version (for example :1.0.21) rather than a caret range until you have reviewed what changed. Laravel package discovery should register the service provider automatically, but confirm in the package composer.json whether a provider, facade or config publish step is required. After installing, run your existing test suite and check for published assets, migrations or config files that need reviewing.
- Which Laravel and PHP versions does Nightfall support?
- The published release notes do not state a support matrix, so check the require block in the package composer.json for illuminate/support, illuminate/contracts and php constraints. If those constraints are open-ended or missing, treat the package as untested against your framework version and verify it yourself. Confirm your exact Laravel and PHP combination passes the suite before merging anything.
- What does the Nightfall package actually include?
- The package is described as Laravel with Jetstream, TailwindCSS and Livewire Powergrid, which suggests a bundled application stack rather than a single utility. Jetstream provides authentication and team scaffolding, TailwindCSS provides the styling layer, and Livewire Powergrid provides data table components. Verify in the repository whether these arrive as Composer dependencies, published assets or opinionated starter files, since that changes how invasive the install is.
- Is Nightfall a starter kit or a runtime dependency for an existing app?
- That distinction matters and is not documented in the release notes. If it is scaffolding, it belongs in a new project or a throwaway branch; if it is a runtime dependency, it belongs in the dependency graph and needs constraint review. Test it on a spike branch first and inspect what files it publishes before deciding which category it falls into for your application.
- What changed between Nightfall 1.0.2 and 1.0.21?
- The release note for 1.0.21 contains only a GitHub compare link, with no changelog, upgrade notes or issue references. That gap covers nineteen patch releases, so reconstruct the real changelog by diffing tags and reading commit history between them. Treat the absence of breaking changes as an assumption to test, not a documented fact.
- How can I safely test Nightfall before using it in production?
- Create a throwaway branch, require one pinned version, and run your full test suite against it. Run composer update --dry-run to inspect which transitive dependencies the install pulls in, and diff the package's public surface between the version you would upgrade from and the one you would adopt. The cost is measured in hours, and the diff is a more reliable release note than anything currently published.
- Will Nightfall conflict with my existing Jetstream, Tailwind or Livewire setup?
- Because the stack overlaps with Jetstream, TailwindCSS and Livewire Powergrid, conflicts are plausible: duplicate migrations, competing tailwind.config.js or webpack/vite settings, overridden views, and repeated component registrations. Review every published file individually instead of accepting a blind vendor:publish. Running the install on a branch and diffing the working tree will show exactly what it touches.
- How should I upgrade Nightfall from 1.0.2 to 1.0.21?
- Do not jump nineteen patches at once. Step to the next tagged version you can diff against, read the diff, run the suite, then step again. If a regression appears, git bisect between tags is far cheaper than diagnosing the same problem in production.
- What alternatives exist if I only need part of the Nightfall stack?
- If you only need data tables, use Livewire Powergrid directly; if you only need authentication scaffolding, use Jetstream or Breeze; if you only need utility CSS, install Tailwind yourself. Composing the individual packages gives you a documented support matrix and a smaller blast radius than one bundled dependency. Nightfall mainly saves setup time, which is usually a one-off cost.
- Is Nightfall actively maintained and safe to depend on long term?
- The package comes from a single organisation with no visible contributor base or security policy in the supplied information, which is a genuine bus-factor risk. Before adopting it, check GitHub for recent commits, issue response times and tagged releases with real notes. If you depend on it, pin versions, monitor the repository, and keep a plan for replacing it.
Weaver
How can I help you explore Laravel packages today?