Repository navigation
v0.2.0 — NixPHP is now NAF
NixPHP is now NAF, short for Not Another Framework.
The old name collided with NixOS everywhere it mattered — in search results, in package listings, and most concretely in the shell, where our CLI binary was literally nix. On any machine with Nix installed it could not be called at all.
What changed
| before | after | |
|---|---|---|
| Composer package | nixphp/framework |
naf/framework |
| PHP namespace | NixPHP\ |
Naf\ |
| Base path constant | NIXPHP_BASE_PATH |
NAF_BASE_PATH |
| Plugin package type | nixphp-plugin |
naf-plugin |
| CLI binary | nix |
naf |
| Repository | nixphp/framework |
nafphp/framework |
No API changed and no behaviour changed — with one consequence you have to know about.
Plugins must move with the framework
Plugins are discovered by their Composer package type, and that type is now naf-plugin. A plugin still declaring nixphp-plugin is not loaded — silently, with no error and no warning. Move the framework and every plugin you use in the same step.
Upgrading
composer remove nixphp/framework
composer require naf/framework:^0.2Then rewrite the references in your own code. On macOS:
grep -rl -e 'NixPHP\\' -e 'nixphp/' --include='*.php' --include='composer.json' . \
| xargs sed -i '' -e 's/NixPHP\\/Naf\\/g' -e 's#nixphp/#naf/#g'On Linux, sed -i takes no argument — drop the ''.
The old package
nixphp/framework stays on Packagist, marked abandoned and pointing here. It receives no further releases. The repository at github.com/nixphp/framework is frozen at v0.1.6 and stays where it is, so every existing link keeps working.