1. If you ever run into anything about the lock file, such as error: The source code is invalid, as it does not match the expected hash in the lock file, rebuild the lock file like so

    deno task lock:reset
    
  2. Relatedly, follow these instructions for

    Rebasing because of differences in generated files

  3. If you run into an error like this remote: **error**: Module not found "file:///app/routes/reset.ts", it’s likely because you forgot to run deno task start before deploying

  4. Run the REPL! deno task repl The following will refresh a doctor’s tokens, for example

    const google = await import ("./external-clients/google.ts")
    const doctors = await import("./models/doctors.ts")
    const db = (await import("./external-clients/db.ts")).default
    
    const [doctor] = await doctors.getAllWithTokens(db)
    
    google.refreshTokens(doctor)
    
  5. To add a remote repository to your local Git configuration try: heroku git:remote -a <app-name> This is useful if you’re asked to provide -a or —app <app-name> when using commands such as deno task chatbot:down || deno task chatbot:up Document for heroku / git configuration

  6. If you’re not sure why a kysely query is giving you unexpected results, you can get the SQL with console.log(query.compile().sql)

  7. If you run into instances where your dev or test database is mucked up, you can go to the main branch, and then drop and and rebuild your databases to get back to a known good state like so

    dropdb vha_dev
    dropdb vha_test
    ./setup.sh