bug: Console Logs not showing for Next.js backend

[moritzWa]

Provide environment information

System:
    OS: macOS 14.4.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 689.95 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.0 - ~/.nvm/versions/node/v20.12.0/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.0/bin/npm
    pnpm: 9.1.0 - ~/.nvm/versions/node/v20.12.0/bin/pnpm

Describe the bug

I'm not seeing any of the console logs I put in my routes.

I know this repo implements loggerLink, but is insufficient.

Maybe this is due to the "terminal tubro ascii layout"?

I noticed that the default outputMode for turbo is full which "Displays all output (default)"

So, both of these did nothing:

1. adding --output-logs=full to the dev script
2. adding "outputMode": "full" to the dev pipeline in the turbo.json

Example of stuff I'm trying to log:

Link to reproduction

n/a (haven't made any significant changes to the template)

To reproduce

1. add logs to route like post.ts
2. run pnpm run dev
3. see if they appear in the console

Additional information

No response

[moritzWa]

Also, pls lmk if I should post this in the main t3 repo or the turbo repo instead.

[RedBeardEth]

As indicated in the first picture - you need to use the arrow keys to navigate up from @acme/api to @acme/nextjs @moritzWa

[moritzWa]

ohh, thank you! Should I add a sentence about this to the README? Or change this text to "Use arrow keys to navigate between packages". (Not just "Use arrow keys to navigate.)

[juliusmarminge]

Doesnt the UI say?

[moritzWa]

@juliusmarminge is there a way to make the logged content full height? Is this part of turbo?

[moritzWa]

ok nvm found this https://github.com/vercel/turbo/discussions/7802

[juliusmarminge]

should be better in turbo 2.0

[juliusmarminge]

closing as this is not related to here, but like i said the TUI mode is better / less buggy in 2.0 where it's no longer experimental