When building web applications for a global audience, it is important to consider localization—the process of presenting your web application's con...
For further actions, you may consider blocking this person and/or reporting abuse
Fantastic article! Definitely opinionated, but Lingo.dev is fire ;) 🔥
By the way, quick tip:
To extract translation strings, one can just use the following prompt with claude sonnet:
Works like magic!
Ouuuuu! I didn't know that. Thank you for the tip, Max!
That prompt is a lifesaver 🚀 I often use similar one directly in Cursor IDE 🙃
Nice article 🚀🚀🚀
Well, if you are, give me a shout and we can have a look at how the
authcommand works together.Or you can just put your Lingo.dev API key into
LINGODOTDEV_API_KEYenv variable. Windows does have those, right? Genuinely asking 🫥Hi, Matej. Thank you!
I wouldn't mind looking at how the auth command works with you.
Yes, Windows have those. 😅 But then, the problem persists when you run other commands like,
npx lingo.dev@latest init. So I figured it was better to run the commands from a Unix-like environment.Did you try running the CLI directly on Windows? Do you have node installed? It is written in typescript / node, not bash. But honestly we did not check on Windows.
I am happy to hear you got it running via WSL. Is that the standard for developing on Windows? Or is direct support for Windows preferred?
I initially tried running the CLI directly on Windows and have Node installed. However, each command attempts to run a Bash script located in
node_modules/.bin/lingo.devfor some reason. Since Windows does not natively support running Bash files, it simply opens the file in a text editor, browser, or whichever default program the user has set. I can paste the file's content if you want.From my experience, most developers use WSL or Git Bash frequently because this issue is not unique to Lingo. Windows support would be nice, but I wouldn’t prioritize it too much. There’s a high chance developers will encounter the same issue with another package and eventually switch to WSL.
I tried to run this on my gaming machine out of curiosity. I learned that while via
npxit tried to run the bash script, installinglingo.devvia npm worked (it created a.cmdcomamnd). However not all of the CLI commands worked.If this works via WLS, I think we can check the Windows platform support ✅
Thank you for your help 🙌
This is interesting because I did try to install lingo.dev via npm and even though it installed, I couldn't perform the authentication and other CLI commands
Definitely. Windows is "interesting" to build for. 😅
You're welcome! And thank you too!
Lingo.dev now has a Compiler that makes localization much much easier.
You can see it on X @lingodotdev 🤩
For sure! I'll probably write a tutorial about it after testing. Lovely stuff from the Lingo.dev team!
Thank you, Ademola 😊🙏
Looking forward to read the tutorial.
Have you tried the lingo.dev compiler 🤔
Check it out on X @lingodotdev 👌