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
{{ message }}
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
Running Windows 10 Pro with Docker Desktop using WSL2. VSC is 1.45.1.
From the command prompt (cmd.exe) I can initiate a Wordup instance successfully but the VSC extension isn't working.
It will prompt me for the information (e.g. project name, whether it is a plugin, location, etc.) and it acts as if it successfully created it but when navigating into the folder no files are there and when attempting to load the folder via the extension it doesn't see it as there nor can it install the local dev server (erroring out that the location doesn't exist).
Even after creating the Wordup instance manually, opening the instance folder does not result in anything showing up in Wordup's extension tab and refreshing the Wordup tab doesn't help either.
Any ideas?
The text was updated successfully, but these errors were encountered:
Running Windows 10 Pro with Docker Desktop using WSL2. VSC is 1.45.1.
From the command prompt (cmd.exe) I can initiate a Wordup instance successfully but the VSC extension isn't working.
It will prompt me for the information (e.g. project name, whether it is a plugin, location, etc.) and it acts as if it successfully created it but when navigating into the folder no files are there and when attempting to load the folder via the extension it doesn't see it as there nor can it install the local dev server (erroring out that the location doesn't exist).
Even after creating the Wordup instance manually, opening the instance folder does not result in anything showing up in Wordup's extension tab and refreshing the Wordup tab doesn't help either.
Any ideas?
The text was updated successfully, but these errors were encountered: