html5 example help
hey all. quite new to this stuff, and was trying to follow the html5 quickstart guide but it errors out when i run
npm run dev.
any help is genuinely appreciated. thanks!11 Replies
[rivet:dev] 'rivet' is not recognized as an internal or external command, [rivet:dev] operable program or batch file.
[client:dev] 'vite' is not recognized as an internal or external command, [client:dev] operable program or batch file.it seems you dont have the rivet CLI nor vite installed, did you make sure to install rivet via and run
npm install?i did run those commands to install the rivet cli and ran
npm install.
it says to Add the directory containing rivet.exe to your PATH environment variable. in the quickstart which i missed the first time i tried this, and im thinking thats the issue. how would i go about doing this? thanks for your time hahaon windows you can add to the PATH with from
cmd, or from powershell. just replace the path with wherever rivet.exe is located
if you prefer to use a GUI instead heres a tutorial https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/Add to the PATH on Windows 10 and Windows 11 | Architect Ryan
Thoughts from Ryan Hoffman, an experienced team leader, software architect and developer.
that might not solve your error with vite, thats supposed to be installed after
npm installadded the directory to the PATH env, however npm run dev is still returning the same error, saying that it doesnt recognize rivet or vite as an internal or external command
tried to redo the process in a completely new folder and produced the same results.
if you try to run
C:\path\to\rivet.exe --version do you get the same error?i get:
when i try to run the same command in
C:\path\to\rivet.exe\toolchain\examples\html5-node\ i get the rivet is not recognized errordoes your PATH contain
C:\path\to\rivet.exe or C:\path\to? the latter is what you'll want. besides that i would try restarting your terminal and trying againthat seemed to fix it. now i am just having issues with vite and it not being recognized as a command. it seems like
npm install didn't fully do its job
figured it out! had to do with the version of node i was using. thanks so much for the help!no problem! glad we could help