npm i -g firebase-tools leads to ...firebase.ps1 cannot be loaded because running scripts is disabled on this system

[Adam-Ponting]

I've come across the following error today after updating firebase-tools.
I use Visual Studio Code and after the latest firebase update I'm not able to run any firebase scripts in the PowerShell terminal.
I can run them in cmd and I can run other scripts still in PowerShell, eg npm and Netlify hosting.
I was using firebase in one project after deploying earlier today, got the prompt to update firebase-tools, did so, and now cant access firebase in any project from PowerShell.
Been using without issue for 6+months.

[REQUIRED] Environment info

• firebase-tools@7.2.4

// Can't run this command but package.json says:
"firebase": "^5.11.1",

Platform:
Windows 10 Home

[REQUIRED] Test case

1. Install Visual Studio Code
2. Open a new file/folder
3. In terminal -
   npm install -g firebase-tools
4. In PowerShell terminal -
   firebase // followed by any command
   leads to error :
   firebase : File C:\Users\mada7\AppData\Roaming\npm\firebase.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.

[REQUIRED] Steps to reproduce

As above

[REQUIRED] Expected behavior

firebase to run scripts in powershell, which worked until updating firebase-tools to the latest version.

[REQUIRED] Actual behavior

// can't run with --debug flag in Powershell
PS C:\web-dev\cv> firebase
firebase : File C:\Users\mada7\AppData\Roaming\npm\firebase.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.
At line:1 char:1

• firebase

•   + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
  
  

// running in cmd
Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\web-dev\cv>firebase --debug
[2019-08-27T08:50:01.286Z] ----------------------------------------------------------------------
[2019-08-27T08:50:01.290Z] Command: C:\Program Files\nodejs\node.exe C:\Users\mada7\AppData\Roaming\npm\node_modules\firebase-tools\lib\bin\firebase.js --debug
[2019-08-27T08:50:01.291Z] CLI Version: 7.2.4
[2019-08-27T08:50:01.291Z] Platform: win32
[2019-08-27T08:50:01.292Z] Node Version: v10.16.3
[2019-08-27T08:50:01.293Z] Time: Tue Aug 27 2019 09:50:01 GMT+0100 (British Summer Time)
[2019-08-27T08:50:01.293Z] ----------------------------------------------------------------------

Usage: firebase [options] [command]

[samtstern]

@abeisgoat any idea what's going on here? This is a Windows thing, so I am therefore automatically scared of it.

[jwv]

I have the same error.
Temp solution:
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser

[ImDaHeat]

I have the same error.
Temp solution:
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser

is it safe?

[jwv]

I have the same error.
Temp solution:
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser

is it safe?

Unfortunately it's not safe. If you choose use this police very careful when use package manager like chocolatey.

[Adam-Ponting]

So, I updated vue.js later in that day and got errors running those scripts too.
Posted the problem on the Vue forum and got directed to Stackoverflow, a user on there replied with a similar workaround, which I've reluctantly done.
https://stackoverflow.com/questions/57673913/vsc-powershell-after-npm-updating-packages-ps1-cannot-be-loaded-because-runnin

[claytonsurgeon]

Ran into this issue updating from 7.3.1 to 7.3.2

[mohsinraza2223]

I have the same error.
Temp solution:
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser

It's a good solution and works for me.

[pebojote]

I have the same error.
Temp solution:
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser

is it safe?

Unfortunately it's not safe. If you choose use this police very careful when use package manager like chocolatey.

Well, try this:

PS C:> Set-ExecutionPolicy RemoteSigned

Then run your chosen firebase syntax command.

[amit-kumar-dubey]

used this Set-ExecutionPolicy RemoteSigned that work for me.
thanks

[pritamshinde]

After the effort, I think Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser is good option to fix the issue.you can go with this it will not create issue.

[pritamshinde]

If you try to generate command on cmd it will be work instead of VS Code Terminal.

[rajachennupati]

Remove ng.ps1(respective ps1 file) from the directory C:\Users< username >\AppData\Roaming\npm\ then try clearing the npm cache at C:\Users< username >\AppData\Roaming\npm-cache..

this worked for me

[saif01]

Remove firebase.ps1(respective ps1 file) from the directory C:\Users< username >\AppData\Roaming\npm\ then try clearing the npm cache at C:\Users< username >\AppData\Roaming\npm-cache.. ( npm cache clean --force )

this worked for me

[DavidHCox]

Remove ng.ps1(respective ps1 file) from the directory C:\Users< username >\AppData\Roaming\npm\ then try clearing the npm cache at C:\Users< username >\AppData\Roaming\npm-cache..

this worked for me

@rajachennupati's way 100% works. Do what he said above and delete that .ps1 file (aka Windows Powershell Script) and then run the command npm cache clean.