By the way to get to this point I had to run this in a Terminal window to get the permissions to run the original script(s)
@stobot maybe this would help?
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
before running NPM
By the way to get to this point I had to run this in a Terminal window to get the permissions to run the original script(s)
@stobot maybe this would help?
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
before running NPM
You seem to have added a space after the first word set -
, remove it and try again/
Actually I added the space because when I tried it originally it showed the below, so I though that was a typo.
Sorry, I did it inside a “Windows powershell” console.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Users\antho>
^ Powershel prompt
Ah, thanks. Ran it in Powershell as described.
Trying the install again though doesn’t seem to be any different, same error messages on my end.
I am a newby with this as well and still have my own problems above
I can confirm the exact same error with my Windows 11 - powershell scripts, if I try to start the server.
Initially I did use node.js 22.12 then changed to 22.14 → no difference
I used the How to run documentation to install the app.
There seems to be a localhost_certs.sh file, which is not compatible with Windows. So if localhost.cnf
is needed, it can not work.
@pmario @stobot @TiddlyTitch @TW_Tones
The URL_INVALID error was a prisma regression, so I locked the version at one that works. Please try again.
@Arlen22 … I did re-install everything. But no changes. Still the same error.
Did also checkout the dev environment. → Same problem
It’s working for me. My exact steps are:
npm init @tiddlywiki/mws@latest mws-run-2
cd mws-run-2
npm start