PHPackages beromir/neos-ray - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Debugging & Profiling](/categories/debugging) 4. / 5. beromir/neos-ray ActiveNeos-package[Debugging & Profiling](/categories/debugging) beromir/neos-ray ================ Debug your Neos site with the Ray app. v1.5.0(1y ago)3537GPL-3.0PHPPHP ^7.3 || ^8.0 Since Oct 5Pushed 1y ago1 watchersCompare [ Source](https://github.com/beromir/Beromir.Ray)[ Packagist](https://packagist.org/packages/beromir/neos-ray)[ RSS](/packages/beromir-neos-ray/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (8)Dependencies (3)Versions (9)Used By (0) Ray Helper for Neos CMS ======================= [](#ray-helper-for-neos-cms) Debug your Neos site with the Ray app. Ray is a debugger app from Spatie. You can find more information about Ray on . Official Ray docs: . Installation ------------ [](#installation) Run the following command in your site package: ``` composer require --no-update beromir/neos-ray ``` Then run `composer update` in your project root. Requirements ------------ [](#requirements) You need to have the Ray app installed and a valid license. You can download the app here: . Configuration ------------- [](#configuration) Create the configuration file `ray.php` in your Neos site root directory. Configuration options: . Configuration options when you use Docker: . Usage ----- [](#usage) You can use all Ray functions from . Reference list (just the PHP specific functions): . To use the functions, you must add them as key-value pairs in Fusion. If the function does not require any parameters, you can use `null`, `false` or an empty string as the value. To pass parameters, add them as a value. ``` valueToDebug = 'Show this text in the Ray app.' valueToDebug.@process.debug = Beromir.Ray:Debug { // Show a label in the Ray app label = 'Text' // Colorize the output red = '' // Show the output as large text large = '' } ``` ``` valueToDebug = 'Show this text in the Ray app.' valueToDebug.@process.debug = Beromir.Ray:Debug { // Show a label in the Ray app label = 'Text' // Only send a payload once when in a loop once = ${node} } ``` **Debug a Fusion expression:** ``` valueToDebug = 'Show this text in the Ray app.' valueToDebug.@process.debug = Beromir.Ray:Debug ``` Alternative ways: ``` // Debug the current node debug = Beromir.Ray:Debug { value = ${node} } renderer = afx` {props.debug} ` ``` ``` renderer = afx` ` ``` **Debug multiple values:** ``` debug = Beromir.Ray:Debug { // Pass the values as an array value = ${[node, site]} } renderer = afx` {props.debug} ` ``` **Use Debug Actions to debug NodeTypes:** ``` // Display the NodeType name of the node debug = Beromir.Ray:Debug { value = ${node} debugAction = 'nodeTypeName' } renderer = afx` {props.debug} ` ``` ``` // Display the properties of the current node and the site node debug = Beromir.Ray:Debug { value = ${[node, site]} debugAction = 'properties' } renderer = afx` {props.debug} ` ``` You can use the following Debug Actions for NodeTypes: Debug ActionDescription`nodeTypeName`Display the NodeType name of a node`context`Display the context of a node`contextPath`Display the context path of a node`properties`Display the properties of a node### Eel Helper [](#eel-helper) You can also use the Ray Eel helper to debug your site. ``` {Beromir.Ray.debug(node)} {Beromir.Ray.debug([node, site])} ``` The second parameter can be used to set a debug action for NodeTypes. ``` {Beromir.Ray.debug(node, 'properties')} ``` ### Health Score 37 — LowBetter than 83% of packages Maintenance45 Moderate activity, may be stable Popularity20 Limited adoption so far Community7 Small or concentrated contributor base Maturity61 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~180 days Recently: every ~306 days Total 8 Last Release 423d ago PHP version history (2 changes)v1.1.1PHP ^7.3|^8.0 v1.4.0PHP ^7.3 || ^8.0 ### Community Maintainers ![](https://www.gravatar.com/avatar/9684d477fcb2b45b91e1c92c7cf3d439388a4c555e2cfff10e5bc188226c4f2b?d=identicon)[beromir](/maintainers/beromir) --- Top Contributors [![beromir](https://avatars.githubusercontent.com/u/45039929?v=4)](https://github.com/beromir "beromir (21 commits)") --- Tags debugneos-fusionneoscmsraydebuggingflowNeos ### Embed Badge ![Health badge](/badges/beromir-neos-ray/health.svg) ``` [![Health](https://phpackages.com/badges/beromir-neos-ray/health.svg)](https://phpackages.com/packages/beromir-neos-ray) ``` ### Alternatives [spatie/ray Debug with Ray to fix problems faster 62242.5M758](/packages/spatie-ray)[spatie/global-ray Enable Ray in all PHP files on your system 21863.0k1](/packages/spatie-global-ray)[sandstorm/plumber Profiling Toolkit for Neos Flow and Neos 384.9k](/packages/sandstorm-plumber)[spatie/wordpress-ray Debug WordPress apps with ease 799.1k](/packages/spatie-wordpress-ray)[shel/nodetypes-analyzer Graphical analysis & visualizer for the Neos CMS nodetypes as backend module 2160.6k](/packages/shel-nodetypes-analyzer)[mmucklo/krumo KRUMO - version 2.0 of print\_r(); and var\_dump(); (with new updates) 89168.0k6](/packages/mmucklo-krumo) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)