-
Notifications
You must be signed in to change notification settings - Fork 20
Windows support #5
Comments
When the gem file is installed for theme you can locate it using the windows command Important is how the response returns all known paths, even if multiple exist. Ideally I believe the .bat is preferred where possible. |
Hi @YourWishes, I'm a Windows user and was wondering what the status is of the PR? When I install Theme Check in VSC I get this notification: "The 'shopify' executable was not found on your $PATH. Was it installed? The path can also be changed via the "shopifyLiquid.shopifyCLIPath" setting." Until Theme Check supports Windows, is there any way for me to manually add the $PATH in the extension settings, and do you know what the paths are for Shopify CLI and the Language Server? Thanks! |
I'm picking this up this week. Coming soon :) |
Some notes: I've found that ruby on Windows is 3x slower than on Linux 😢. The two above PRs assumes that you installed theme-check on Windows (cmd or powershell). This means that, as a Windows user, because ruby is slower on Windows, checks will come in 3x as much time. I've experienced 5s on Windows Subsystem for Linux (Ubuntu) and 15s on cmd.exe on a 2019 macbook pro running Windows via bootcamp. There might be a way to go around this by using Windows Subsystem For Linux, but I'm no Windows wiz so I'm not too sure how we'd set that up in the VS Code extension. Plus, I fear that would make the installation steps a tad complicated. Might be OK if we dump that info in a TROUBLESHOOTING file or something. Would gladly accept help on this, in the meantime it will work. If that's fast enough for you, good :) The Language Server (completions and stuff) shouldn't feel too slow, but it's the checking that I'm slightly worried about. |
https://code.visualstudio.com/docs/remote/wsl#_managing-extensions looks like a good read. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The latest version of theme-check (v1.5.0) should get a Windows user up and running.
Please report any issues! Outstanding issues: There's a bug in |
It works very well now. @charlespwd thank you 😄 |
For anyone coming here because of the visual studio error I got the above issue because I was using theme-check v1.2.0. Upgrading to v1.5.0 removed the issue. |
Has this issue been fixed? |
@charlespwd Any news about this issue? Has it been fixed? It's been holding me back from switching over to using shopify-cli instead of themekit on Windows, for quite some time now. |
I just want to mention the plugin works perfectly for me using WSL2/Ubuntu on Windows 11. My theme files/workspace/theme-check/stylelint/etc are all on WSL, I'm just more comfortable in a Linux shell (and Windows Terminal is quite nice to use). The info on this page helped me understand switching VS Code to run on WSL - https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl |
Technically you're on Linux (not Windows) when you use WSL (WSL2 to be specific). So I don't think it would qualify as "it works on Windows". More of: "It works on virtualized Linux running on a Windows host." |
I just would like add my situation here : |
On Windows 10:
|
Works like a charm! Thanks @Carson-JG |
"shopifyLiquid.languageServerPath": "C:\Users\raihan\AppData\Local\Microsoft\WindowsApps\theme-check-language-server.bat", |
Just wait a week, it'll be baked in the VS Code extension without an out-of-band installation step. It will also get automatically updated from then on. |
@charlespwd please see my latest issue, I believe it's connected with this thread: |
Would need upstream support from Shopify/theme-check first. Not too sure what the implications are. Bat file? No idea.
The text was updated successfully, but these errors were encountered: