如何修复错误-nodemon.ps1无法加载，因为在这个系统上禁用运行脚本，(没有安全风险) ？

I'd recommend using RemoteSigned as opposed to Unrestricted, and limiting the policy to the CurrentUser if possible.

Run Powershell as Admin, and then:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

RemoteSigned: "The default execution policy for Windows server computers."

Other than that, I wouldn't worry about it too much, as it's not intended to be a security mechanism. See this quote from the docs:

"The execution policy isn't a security system that restricts user actions. For example, users can easily bypass a policy by typing the script contents at the command line when they cannot run a script. Instead, the execution policy helps users to set basic rules and prevents them from violating them unintentionally."

There is no security risk whatsoever associated with allowing remoted signed scripts to run on your local machine. It basically means you can execute local unsigned scripts i.e scripts written by you while scripts from a remote source (nodemon in this case) must be signed by a trusted authority.

P.S: If you're on windows, you can just go to settings >> update and security >> for developers >> check the box beside change execution policy to allow local powershell scripts to run without signing

This command might help

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

While using npm I recommend to bridge the nodemon command in the scripts section and leave the security settings as they are.

package.json:

{
"scripts": {
"hmr": "nodemon index.js",
"nodemon": "npm run hmr",
"start": "node index.js"
},
"dependencies": {}
}

Just execute npm run nodemon which will run the hmr line behind the scenes.

For those who are not aware of how to solve this error using Windows PowerShell

1. Open PowerShell (Run As Administrator)
2. Check the current execution policy using this command

    Get-ExecutionPolicy
# You should get 'Restricted'

3. Run this command to make it 'Unrestricted'

    Set-ExecutionPolicy Unrestricted

4. Check again whether execution policy changed by running this command

    Get-ExecutionPolicy
# You should get 'Unrestricted'

5. Now try to run nodemon on your project

    nodemon 'filename.js'

Hope this would be helpful

I've a better solution, just go to the folder where nodemon.ps1 places (path is in error) and delete nodemon.ps1 file.

now go to the terminal and run nodemon -v, if you get a version then the problem solved.

Step 1 : Go to this location --> File C:\Users\Dell\AppData\Roaming\npm
Step 2 : Delete the nodemon.ps1 file and run the command.

This cmd works properly.

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

In windows 10.

Mapped wrong path in Adminstration and system variables for npm. Go to Environment variables and change the those path under PATH variables.

Step 1:

C:\Program Files\nodejs\node_modules\npm to C:\Users\Administrator\AppData\Roaming\npm

Step 2:

Then restart my system.

It works fine.

nodemon: File C:\Users\HP\AppData\Roaming\npm\nodemon.ps1 cannot be loaded because running scripts is disabled on this system. For more
information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.

If anyone who facing this problem...so my opinion is that just go in file and delete the nodemon.ps1 file and then try use nodemon filename

I slove my problem with the following command.

=>run PowerShell as administrator

=>run following command

get-ExecutionPolicy

=>if restricted; run the following command

set-ExecutionPolicy Unrestricted

=>and set to all

=>again check by foll. command

get-ExecutionPolicy

it will get unrestricted and problem is solved

Go to the folder : - C:\Users\admin\AppData\Roaming\npm

Delete the powershell file of nodemon or nodemon.ps1 . You will be good to go.

You can do this by without changing the policy. C:\Users\HP MICROTECH\AppData\Roaming\npm\nodemon.ps1 (path is given at error screen)

just go to this path and delete nodemon.ps1

and there your nodemon runs.

Run these commands:

1. set-ExecutionPolicy RemoteSigned -Scope CurrentUser
2. Get-ExecutionPolicy
3. Get-ExecutionPolicy -list

Go to this link and then follow the steps.

Open Powershell as run as administrator and then run the below commands:

PS> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine


PS> Get-ExecutionPolicy


RemoteSigned


PS> .\Start-ActivityTracker.ps1


.\Start-ActivityTracker.ps1 : File .\Start-ActivityTracker.ps1 cannot be loaded.
The file .\Start-ActivityTracker.ps1 is not digitally signed.
The script will not execute on the system.
For more information, see about_Execution_Policies at https://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\Start-ActivityTracker.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess


PS> Unblock-File -Path [Your Path where the problem found]


PS> Get-ExecutionPolicy


RemoteSigned

The best way to get rid of this error is
Run the below command in your windows power shell as admin

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Basically it will ask you to change the execution policy then type Y .

                  **OR**

You can do is without changing your execution Policy

1. Install nodemon using this command : npm i nodemon -g
2. then type nodemon -v you will see a path in first line of error go to that path then delete that nodemon.ps1 file or filename with.ps1xml extension.

Make sure that you are installing nodemon globally For more details microsoft execution policies docs

Faced Similar issue while running some node command. AppData\Roaming\npm\serverless.ps1 cannot be loaded because running scripts is disabled on this system.

PS C:\Users\adas67> Get-ExecutionPolicy
Restricted


PS C:\Users\adaaa> Get-ExecutionPolicy -List


Scope ExecutionPolicy
----- ---------------
MachinePolicy       Undefined
UserPolicy       Undefined
Process       Undefined
CurrentUser       Undefined
LocalMachine       Undefined

Solved by this.

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

This solved mine.

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

and maybe this is more secure as is only restricted to the current user.