@adam, any thought why I am still receiving the following error message although the CodeEditor module is showing up under Components on the admin page (like the screenshot @irortiz posted) as well as showing as installed in VSCode? The line I’m having issues with is “New-UDCodeEditor -Id ‘codeEditor’ -ReadOnly -Height 500” as you used in Get the output from script "live" in dashboard? - #14 by adam
The term “New-UDCodeEditor” is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Figured it out! Although the path to the components show C:\ProgramData\PowerShellUniversal\Dashboard\Components and I confirmed that the module was in that location, it wasn’t until I added the module to “C:\Program Files\WindowsPowerShell\Modules” that the code editor started working in the dashboard and the cmdlet was recognized.
I’m still figuring out what the essential locations are as far as where I need to store the modules in order for them to work properly, but that is for another discussion.