You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(compiler): move translation service initialization to see the logs (#1705)
* feat: move translation service initialization to see the logs
We don't really need to initialize it inside the server,
since server is only a way to use the service in the dev mode.
Logs of the server are written to a file due to it being started
from process which doesn't have access to console.
But we want to see TranslationService initialization logs
in the console, and the clearest way is to start it early,
rather than extracting validation into a separate function.
* fix: new ai sdk api compatibility
* chore: add changeset
* feat: add compiler e2e tests
* fix: run tests preparation through turbo
* fix: limit installed browsers to chromium and fix trubo config
* fix: run build before tests
* fix: get rid of noisy logs
* fix: cleanup logs and unused functions
* fix: compiler version in next demo
---------
Co-authored-by: Max Prilutskiy <5614659+maxprilutskiy@users.noreply.github.com>
@@ -205,14 +206,12 @@ export async function withLingo(
205
206
`Initializing Lingo.dev compiler. Is dev mode: ${isDev}. Is main runner: ${isMainRunner()}`,
206
207
);
207
208
208
-
// TODO (AleksandrSl 12/12/2025): Add API keys validation too, so we can log it nicely.
209
-
210
209
// Try to start up the translation server once.
211
210
// We have two barriers, a simple one here and a more complex one inside the startTranslationServer which doesn't start the server if it can find one running.
212
211
// We do not use isMainRunner here, because we need to start the server as early as possible, so the loaders get the translation server url. The main runner in dev mode runs after a dev server process is started.
0 commit comments