tl;drWhen attempting to run solution init in my plugin folder, I’m getting the following:solution : The term 'solution' is not recognized as the name of a cmdlter, 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.At lin:1 char:1+ solution init+ ~~~~~~~~ + CategoryInfo : ObjectNotFound: (solution:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException BackgroundI’m going to preface by saying that I’ve gone through and successfully published an XM Solution to my sandbox brand once before using an individual installation of Node (didn’t use nvm). When I got on about a month later, I became aware of being out-of-date on Node, so after dealing with the unsurety of cleaning things up properly (uninstalling prior version of Node and using new one), I tried to remove all my prior setup and start clean with an nvm installation. Actions taken during my removal of past setup is what I anticipate is now giving me trouble. Here’s where I’m at: I get through creating my extension and its plugin. I navigate to the plugin directory and run thenpm installandnpm install --location=global @qualtrics/solution-cliThose both appear to run successfully. Additionally, I have added Solution CLI to the environment path (I’m operating in Windows) - C:\Users\<username>\AppData\Roaming\npm\bin. I did have it in either the System variables or User variables, but I have put it in both since things weren’t working. The next step is to initialize the Solution CLI, but this is where I got the aforementioned error at the start of my post. I will note that when setting up the environment path, I noticed I didn’t have the npm folder and bin sub-folder in ~\AppData\Roaming, so I manually created the npm folder and contained bin folder. Should those have been automatically created during my npm install step, and the fact that they weren’t already there indicative of my issue? I have used the nvm to uninstall node, removed the nvm, re-installed the nvm, and re-done everything with nvm (allowing Chocolatey to do its thing, as well). I’ve done a version check to make sure I have the most-recent LTS version of Node. I’ve created a new extension folder and plugin, but still got stopped at this point every time. Any ideas to help me out?

Well, I just proved at least one idea right - set my Environment Variables PATH to include C:\Users\<username>\AppData\Roaming\nvm\<current node version>\binSo mine looked like C:\Users\<username>\AppData\Roaming\nvm\v20.9.0\bin. Added it to the Path, restarted PowerShell, navigated to my plugin directory, ran npm install and npm install --location=global @qualtrics/solution-cli, then ran solution init and was prompted to log in! I might have figured it out. This leads me to the unpleasant conclusion, though, that I’ll have to update the Environment Variables each time node updates. I tried a generic Path of C:\Users\<username>\AppData\Roaming\nvm already to no avail, so I probably just learned something others already know about how specific paths need to be, which becomes difficult with nvms and changing versions.

Solution CLI not installing? | Experience Community

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded