monorepo: [bug] VSCode extension : "command "inlang.extractMessage" not found"
Problem
After installing the official latest Inlang extension (inlang.vs-code-extension v1.21.0) on a fresh inlang Sveltekit project :
https://github.com/MarArMar/SvelteInlang
If running command from command pallette I have the error modal :
Command “inlang: Extract Message” resulted in an error command “inlang.extractMessage” not found
Other commands fail as well
VSCode extension status page : Activation Event:Startup Activation Time:118ms
If I uninstall all other extentions, uninstall Inlang, install inlang again, reload VSCode, even closing all VSCodes & reopening a fresh one, I get : Activation Event:onStartupFinished Activation Time:72ms
And still the same error on commands
Expected behavior
Commands work
Reproduction
- Clone https://github.com/MarArMar/SvelteInlang
- pnpm install, pnpm dev to check if it works
- Install inlang extension
- Try to run the command “inlang: Extract Message”
Other information
Windows 10 VSCode version 1.84.2
Maybe something I thought of :
I see this activation event :
workspaceContains:**/project.inlang.json
But I had a readme saying “project.inlang.json” shouldn’t be used so I changed
Anyway I tried both with project.inlang.json & project.inlang/settings.json and both didn’t work for me
-
If I disable, re enable the VSCode extension, I see the message in the bottom bar : “inlang’s extension activated” but still the same error
-
I do not see any context tooltips if I hover over paraglide messages in my code
-
I do see the documentation of params, like :
const greeting: (params: {
name: {};
}, options?: {
languageTag?: "en" | "de" | undefined;
}) => string
This message has been compiled by [inlang paraglide]
Don't edit the message's code. Use the [inlang ide extension], the [web editor] instead, or edit the translation files manually.
The params are NonNullable because the inlang SDK does not provide information on the type of a param (yet).
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 27 (10 by maintainers)
Hey @SebbeBroman @FredBuild @MarArMar I’ll look into this today 😃
🎉🎈 @Gernii has been awarded $20! 🎈🎊
Can’t reproduce this on Mac, unfortunately.
Again, the internally used fs is likely striking back. We’ll find a solution for it and try to fix it.
@felixhaeberle here : https://github.com/MarArMar/SvelteInlang
@MarArMar Same issue happened to me here. When I switched to another VSCode profile and then switched back, the issue was solved.