#all lila dev logs in one place

8 messages · Page 1 of 1 (latest)

severe lintel
# 
12:46:00 [tsc] - Done - Watching...
12:46:01 [esbuild] - Done - Watching...
12:46:01 [bleep] - Done in 17.461s
12:46:08 [tsc] - ✘
12:46:08 [tsc] - Found 1 error - Watching...
12:46:09 [tsc] - Done - Watching...
12:46:10 [esbuild] - Done - Watching...
12:46:14 ERROR scalafmt: /home/thib/lila/app/Env.scala:179: error: [dialect scala3] ; expecte
d but . found
 i lila.common.Uptime.startedAt.unit
       ^
12:46:14 INFO  compiling lila (1 scala source)
12:46:14 INFO  time: compiled lila in 0.42s
12:46:23 INFO  compiling lila (1 scala source)
12:46:23 INFO  time: compiled lila in 0.43s
Stopping lila...
9663/tcp:            605638
Stopped lila.
Started lila.
Configuring logback with file:/home/thib/lila/conf/logger.dev.xml
[info] boot - lila Dev   / scala 3 / java 17.0.5, memory: 512MB
#

Here you can see the combined outputs of:

  • tail -F .metals/metals.log bloop/metals logs of compiling the lila backend - scala
  • ui/bleep -w logs of compiling the lila frontend - typescript and scss
  • journalctl --user -fu lila -o cat lila runtime logging using lila.log and println
#

meaning you get all the dev logs you need mixed in a single terminal stream

#

it can be invoked with npm run multilog from lila's root. You'll need to have the multitail program installed

winged obsidian
#

this looks cool - i might add a target for just metals and bleep. question, should we look at ditching yarn?

severe lintel
#

Niklas has said that now that npm has caught up (with package caching iirc), we no longer have good reasons to use yarn