uuid: - value: dfe87217-dc3b-413c-9e42-912386be5d5f langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:16+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: 'Watching all the things' created: - value: '2024-03-22T00:00:00+00:00' changed: - value: '2025-05-11T09:00:16+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/03/22/watching-all-the-things langcode: en body: - value: |
In yesterday's email, I mentioned that I use watch commands such as nodemon
, watchexec
and entr
whilst developing to run commands automatically when I change code.
For example, running find web/modules/custom | entr ./run test
will re-run my test suite when any custom module changes.
This works well for tests, but for other checks, such as static analysis with PHPStan or coding standards with PHPCS, I have integrations in Neovim, and I get real-time feedback as I code.
If a line fails static analysis or coding standards, a diagnostic message is shown so I can fix it immediately, and I don't need to use a watcher or wait for my CI pipeline to fail.
format: full_html processed: |In yesterday's email, I mentioned that I use watch commands such as nodemon
, watchexec
and entr
whilst developing to run commands automatically when I change code.
For example, running find web/modules/custom | entr ./run test
will re-run my test suite when any custom module changes.
This works well for tests, but for other checks, such as static analysis with PHPStan or coding standards with PHPCS, I have integrations in Neovim, and I get real-time feedback as I code.
If a line fails static analysis or coding standards, a diagnostic message is shown so I can fix it immediately, and I don't need to use a watcher or wait for my CI pipeline to fail.
summary: null field_daily_email_cta: { }