watchman VS fwatch.nvim

postCreateCommand This section permit to execute a command after the build of the container. I've used this command to execute a script to install Expo and other dependencies like watchman

Facebook open source product: https://github.com/facebook/watchman to get notified when configuration, file or other change

Facebook Meta's Watchman Service looks very useful for watching for changes in files and directories to kick off automation. Still, there seem to be a bunch of gotchas with it that only come to light after trying to mess with it. The docs seem lacking, the Python library needs to be updated, and even the installation on non-Ubuntu or Red Hat distros requires a rebuild, which has been somewhat problematic given the build tools. Also, no official Docker container.

Not to be confused with Facebook’s file watch daemon, which does the same sort of thing but is more complicated. There’s a bunch of tools that integrate Facebook’s watchman for more efficient change tracking.

https://facebook.github.io/watchman/

You can also setup file watchers with uv/vim.loop, there's a basic example implementation here, which could be used to recompile & apply whenever pywal.json was updated.

I don’t use NeoVim but this look like it could work.

(If you want buid-on-save, you could use fwatch.nvim, your own libuv wrapper, entr, or any other watcher. Automatic building is out-of-scope for Shipwright.)

The author of fwatch.nvim showed me how easy it was to use libuv to watch files and directories, and after a few days I've been able to implement the feature. It still needs more work and real-world testing, but the fact that a novice like me was able to get this working inside Neovim (and in a couple of hundred lines of code) is astounding.

It's called fwatch.