While Lando will set up tooling routes for the obvious utilities for each application type it tries to not overwhelm the user with all the commands by providing a minimally useful set. It does this because it is very easy to specify more tooling commands in your Landofile.

tooling:
  # Use these in the matching runtime's container
  node:
    service: app
  npm:
    service: app
  ruby:
    service: app

  # And some utilities we installed in the `build.flavor`
  # or `dependencies` key
  grunt:
    service: app
  sass:
    service: app
  drush:
    service: app

Note that the service should match the name of your application in .upsun/config.yaml (or .platform.app.yaml). Very often this is just app.

Node.js and npm belong in a Node.js container; Ruby belongs in a Ruby container. A PHP app gets Node.js only with dependencies.nodejs or a composable Node.js runtime.

Run lando again to see the extra commands.

lando composer      Runs composer commands
lando drush         Runs drush commands
lando grunt         Runs grunt commands
lando node          Runs node commands
lando npm           Runs npm commands
lando php           Runs php commands
lando ruby          Runs ruby commands
lando sass          Runs sass commands

lando drush cr
lando npm install
lando grunt compile:things
lando ruby -v
lando node myscript.js

Check whether a command exists in your application container with lando ssh -c:

# Does yarn exist?
lando ssh -c "yarn"

Also note that Lando tooling is hyper-powerful so you might want to check out some of its more advanced features.