Download the PHP package nyoncode/wire-suite without Composer
On this page you can find all versions of the php package nyoncode/wire-suite. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nyoncode/wire-suite
More information about nyoncode/wire-suite
Files in nyoncode/wire-suite
Package wire-suite
Short Description The whole wire stack in one require, with an interactive installer.
License MIT
Homepage https://wirestack.nyoncode.cz
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package wire-suite
WireSuite
The whole WireSuite stack in one require, and one command that turns a clean Laravel into a working admin.
wire:install finds the parts that are installed, asks which to set up
(everything is pre-selected), and runs each package's own installer rather than a
copy of it. Then it lists the modules this application does not have yet, with
the composer require line for each.
It only runs what has something left to do. A part whose installer has
already written everything it publishes is named and skipped, which is a
correctness rule rather than a speed one: a migration shipped without a date
prefix is stamped when the publish mapping is built, so re-publishing writes a
second copy of one the application already has and migrate then fails on it.
Re-running after adding a module is therefore safe. --force sets up every part
regardless and publishes over what it wrote.
A failed installer fails the command, and --no-interaction reaches the
installers it runs — each of them prompts before touching a production
application, from inside a progress spinner where nobody can answer.
It never runs composer itself. The command runs inside the application it is about to change — the autoloader in use is the one composer would rewrite — and the failure modes (memory, plugins, a production image without composer) are the ones nobody can debug from a stack trace. A line to paste is the honest answer.
What comes with it
| Package | |
|---|---|
| Engine, actions, modals, notifications, widgets, infolists | wire-core |
| Forms | wire-forms |
| Tables | wire-table |
| Drag-and-drop reordering | wire-sortable |
| Resources, pages, routing, zones | wire-panels |
| The admin shell | wire-admin |
Modules, separately
Each is its own require, because an application that wants users and nothing else should not carry a media library:
Then php artisan wire:install again — a module registers itself, so nothing
goes into a config file, and the parts already set up are left alone.
nyoncode/wire-boost (AI agent guidelines, skills and the MCP server) is listed
beside them and never run: wire-boost:install asks which agents to configure,
and that is not a question this command should answer for anyone.
Documentation
Full docs: docs/start/installation.md
(česky).
License
MIT.
All versions of wire-suite with dependencies
nyoncode/wire-core Version self.version
nyoncode/wire-forms Version self.version
nyoncode/wire-table Version self.version
nyoncode/wire-sortable Version self.version
nyoncode/wire-panels Version self.version
nyoncode/wire-admin Version self.version
illuminate/support Version ^12.0|^13.0
nyoncode/laravel-package-toolkit Version ^2.5.2