Weave Code
Neon Laravel Package
nette/neon
NEON is Nette’s human-friendly data serialization format and parser for PHP. It offers a clean syntax for configuration files, supports comments, multiline strings and typed values, and converts NEON to/from PHP arrays and objects with reliable error reporting.
🍸 Encodes and decodes NEON file format.
Frequently asked questions about Neon
- Can I use nette/neon to replace Laravel’s native config files (YAML/JSON/arrays)?
- No, this package is not designed for Laravel. NEON is a Nette Framework format with no native integration for Laravel’s config system. You’d need custom loaders and wrappers, which isn’t recommended due to architectural mismatch.
- How do I install nette/neon in a Laravel project?
- Run `composer require nette/neon`—it’s a standalone package with no Laravel-specific commands. The package provides `Neon::decodeFile()` and `Neon::encode()` methods for parsing NEON files to PHP arrays and vice versa.
- Will nette/neon work with Laravel’s config caching (e.g., `php artisan config:cache`)?
- No, NEON files won’t integrate with Laravel’s caching system. You’d need to manually decode NEON files during runtime, bypassing Laravel’s config caching entirely. This defeats the purpose of caching.
- Does nette/neon support PHP 8.1+ and Laravel 9/10?
- Yes, the package requires PHP 8.0+, which aligns with Laravel 9/10. However, NEON’s syntax (e.g., strict UTF-8, indentation rules) may conflict with Laravel’s permissive handling of config files.
- Can I use NEON files for Laravel’s environment configs (`.env`)?
- No, `.env` files must remain in dotenv format. NEON is for structured configuration, not environment variables. Laravel’s `env()` helper won’t recognize NEON files.
- Are there Laravel-specific alternatives to nette/neon for custom config formats?
- Yes, use Symfony’s YAML component (`symfony/yaml`) for YAML or JSON for simplicity. Laravel already supports these natively. NEON offers no unique advantages for Laravel projects.
- How do I validate NEON files in Laravel (e.g., with PHPStan or Psalm)?
- The latest release (v3.4.8) includes improved phpDoc annotations, which may help with static analysis. However, NEON’s syntax (e.g., multiline strings, typed values) could still trigger false positives in strict tools.
- Will nette/neon break if I upgrade Laravel or PHP?
- The package is stable for minor PHP/Laravel updates, but major version changes (e.g., PHP 9+) could introduce risks. Since it’s not Laravel-specific, updates depend on Nette’s roadmap, not Laravel’s.
- Can I migrate existing Laravel YAML/JSON configs to NEON?
- No automated tool exists. You’d need to manually rewrite configs to NEON’s syntax, which isn’t recommended. The effort outweighs the benefits for Laravel projects.
- Is nette/neon actively maintained for Laravel use cases?
- No, maintenance focuses on Nette Framework. Laravel-specific issues (e.g., config conflicts) won’t be addressed. The package’s phpDoc improvements are internal and don’t solve Laravel integration gaps.
Weaver
How can I help you explore Laravel packages today?