I am using Lando 3.18.0. I have created a Node (version 18) container in my .lando.yml file and set up some tooling so I can run node, npm, and gulp commands. This all works great and I can do things like "lando npm install" and "lando gulp" to run my default Gulp task and it all works great. The only thing that ISN'T working is if I have any kind of Gulp "watch" task. The task starts and it will say something like "Starting 'watchSass'...", but then it essentially just sits there. If I attempt to edit and save something in the watched directory, the watch task does not trigger and re-compile. If I run the same exact gulp file locally with my local Node and Gulp etc, it works fine, but if I attempt to do it with Lando, the watch task just doesn't want to trigger. Here is my .lando.yml file:
So this might be a false alarm. I downgraded my Node version to 16 instead of 18, and now it looks like it is working. I'm not entirely sure why though.
I am using Lando 3.18.0. I have created a Node (version 18) container in my .lando.yml file and set up some tooling so I can run node, npm, and gulp commands. This all works great and I can do things like "lando npm install" and "lando gulp" to run my default Gulp task and it all works great. The only thing that ISN'T working is if I have any kind of Gulp "watch" task. The task starts and it will say something like "Starting 'watchSass'...", but then it essentially just sits there. If I attempt to edit and save something in the watched directory, the watch task does not trigger and re-compile. If I run the same exact gulp file locally with my local Node and Gulp etc, it works fine, but if I attempt to do it with Lando, the watch task just doesn't want to trigger. Here is my .lando.yml file: