search

opral / inlang-paraglide-js

Tree-shakable i18n library build on the inlang ecosystem.
https://inlang.com/m/gerre34r/library-inlang-paraglideJs
48 stars 1 forks source link

[Paraglide-Next] Unclear log in terminal when running next dev #170

Open coderfin opened 4 months ago

coderfin commented 4 months ago

When running next dev after setting up a project using npx @inlang/paraglide-next init a new message is output in the terminal that reads Using existing cloned repo. Unlike the compiling message (ℹ [paraglide] Compiling inlang project at "./project.inlang".) there is no indication that Using existing cloned repo is coming from paraglide, even though it is. It is also unclear what this message means. I believe this message first shows right after the init finishes but why is it showing up when running dev?

It's not a big deal but I think it is a little confusing.

Screenshot 0006-07-11 at 9 36 58 PM
samuelstroschein commented 4 months ago

It's coming from [lix](https://github.com/opral/monorepo/tree/main/lix). prob a task for @jan.johannes

off topic: making the inlang file a binary that is a repo will eliminate those kinds of bugs

samuelstroschein commented 4 months ago

@jan.johannes an inlang file is its own repo. the conditional logic of "does a repo exist", "where is the repo", etc. is gone, and with it debug messages like these