Cannot be loaded because running scripts is disabled on this system -- ANGULAR V14 [closed] - javascript

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 months ago.
Improve this question
When I have to run my Angular project or any ng command, the system shows the below error:
ng : File C:\Users\achra\AppData\Roaming\npm\ng.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
ng v
~~
CategoryInfo : SecurityError: (:) [], PSSecurityException
FullyQualifiedErrorId : UnauthorizedAccess
Any Solution... I'm new on Angular and i have just started to learn !
Thanks for your attention. I’m looking forward to your answers.

First, you have to need to open the command prompt and run this command.
set-ExecutionPolicy RemoteSigned -Scope CurrentUser
Now you have to run the second command on your system. This command is:
Get-ExecutionPolicy
When you have run this command your system has a show “RemoteSigned”. If you have received this message, then your problem will be solved. Now you have to go to the next step to view the list of policy which policy has been updated by the last commands.
To view their policy, you need to run this command in your command prompt:
Get-ExecutionPolicy -list
When you run this command, a few policies are shown on your monitor screen.
Now you can see your system execution policy list. You have successfully solved your problem. Now you need to go to the command prompt and check that your problem is solved.

Related

Error in backblaze b2 axiosRetry is not a function [duplicate]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 15 hours ago.
Improve this question
I am working on a next js 13 application in which I am making an image upload service through the formidable package and the backblaze b2 object storage service, I get this error after starting my application in next js, it worked fine but I've been getting this error for a while now, I've already tried uninstalling the node modules and installing the latest versions of the npm dependencies.
error stacktrace
Critical dependency: the request of a dependency is an expression
Import trace for requested module:
./node_modules/formidable/src/Formidable.js
./node_modules/formidable/src/index.js
./controllers/uploadController.js
./controllers/productController.js
./app/page.jsx
warn - Fast Refresh had to perform a full reload due to a runtime error.
error - node_modules\backblaze-b2\lib\b2.js (24:4) # axiosRetry
error - TypeError: axiosRetry is not a function
at new B2 (webpack-internal:///(sc_server)/./node_modules/backblaze-b2/lib/b2.js:22:8)
at eval (webpack-internal:///(sc_server)/./lib/storageB2.js:8:18)
at (sc_server)/./lib/storageB2.js (C:\Users\fxliv\OneDrive\Escritorio\tuganga\.next\server\app\page.js:1005:1)
at __webpack_require__ (C:\Users\fxliv\OneDrive\Escritorio\tuganga\.next\server\webpack-runtime.js:33:43)
at eval (webpack-internal:///(sc_server)/./controllers/uploadController.js:5:72)
at (sc_server)/./controllers/uploadController.js (C:\Users\fxliv\OneDrive\Escritorio\tuganga\.next\server\app\page.js:983:1)
at __webpack_require__ (C:\Users\fxliv\OneDrive\Escritorio\tuganga\.next\server\webpack-runtime.js:33:43)
at eval (webpack-internal:///(sc_server)/./controllers/productController.js:9:75)
at (sc_server)/./controllers/productController.js (C:\Users\fxliv\OneDrive\Escritorio\tuganga\.next\server\app\page.js:972:1)
at __webpack_require__ (C:\Users\fxliv\OneDrive\Escritorio\tuganga\.next\server\webpack-runtime.js:33:43) {
type: 'TypeError',
page: '/'
}
null
I need someone to help me to continue working on my project, thanks!!

I am trying to create a React Native App with vs code but I have some errors [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 12 months ago.
Improve this question
So this type of the error. How to solve this
Failed to construct transformer: Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:135:10)
at stableHash (/home/shavkat/Android/AwesomeProject/node_modules/metro-cache/src/stableHash.js:19:8)
at Object.getCacheKey (/home/shavkat/Android/AwesomeProject/node_modules/metro-transform-worker/src/index.js:593:7)
at getTransformCacheKey (/home/shavkat/Android/AwesomeProject/node_modules/metro/src/DeltaBundler/getTransformCacheKey.js:24:19)
at new Transformer (/home/shavkat/Android/AwesomeProject/node_modules/metro/src/DeltaBundler/Transformer.js:48:9)
at /home/shavkat/Android/AwesomeProject/node_modules/metro/src/Bundler.js:22:29 {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
The problem is with your node version.
try this solution on github and it should work for you.
Here is two option now -
Try to uninstall Node.js version 17+ and reinstall the Node.js version 16+
Open terminal and paste these as described :
Linux & Mac OS (windows git bash)-
export NODE_OPTIONS=--openssl-legacy-provider
Windows command prompt-
set NODE_OPTIONS=--openssl-legacy-provider
Reference Link

my react-native project is not debug mode [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
My react-native project is not on development mode.
Double tab R key is not working, and cmd + M not working..
My another project is connect to localhost:8081, but my project not connect to localhost:8081 but, build is success.
help me!!
nothing error.
You can run the packager on another port.
react-native start --port=8088
you can also try this
$ adb reconnect
This is not necessary in most cases, but just in case, let's reset your connection with your mobile and restart adb server. Finally:
$ adb reverse tcp:8081 tcp:8081
Then run this command
$ fuser 8081/tcp
You will get a Process id which is using port 8081 Now kill the process
$ kill <pid>
Then run the projectreact-native run-android

Installing Node.js application on CentOS [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have OpenVZ VPS with pre-installed CentOS 6.2 blank (32-bit) and domain name mysite.com. I would like to install Node.js and my javascript application on CentOS that in result should be accessible at mysite.com. So, what steps should I do to implement this? Please, describe process from zero in details. I'm Java developer and have never worked with unix systems :(
Best Regards
"Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications" outside of the browser.
Installing node it self on a system is pretty straight forward. You can simple go to http://nodejs.org and download the correct binary corresponding to your system, or download the source.tar.gz and compile it yourself.
There is a set of installation instructions under the wiki at github.com that will take you through the steps of compiling node on the big three platforms.
I usually will add a prefix when I'm compile so the binaries get moved into the directory I want to store them in. This can be a local directory (ex. $HOME/bin) of the user you want node to be run under or you can make it a system directory where node will be accessible by every user on the system.
$ tar -zxf node-v0.10.3.tar.gz #Download this from nodejs.org
$ cd node-v0.10.3
$ ./configure --prefix=/usr/local/bin
$ make
$ sudo make install
You should now have node and npm installed on the system. From here you can check to make sure everything is working.
$ which node
$ /usr/local/bin/node
$ node -v
$ 0.10.3
$ which npm
$ /usr/local/bin/npm
$ npm -v
$ 1.2.11
With node you will be building your server from the ground up. There are a lot of libraries to help you do this. The main built in one would be http which is built on top of net.
To get your application accessible from your domain you simply need to start your node application and tell it to listen on a port (assuming http, or some networked app). On the linux side you also need to make sure what ever port your node process is listing on is open so connections can be made to your server. The most common firewall on linux system is Iptables.
I'm not a Java developer so I don't know the normal work flow for deploying a Java applet is or how its served so I can't help you bridge the cap there.
This should get you started.

Testacular error: Cannot start chrome [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am going through AngularJS tutorials, and I am stuck on the tutorial for running Testacular tests. I get the following error:
Starting Testacular Server (http://vojtajina.github.com/testacular)
-------------------------------------------------------------------
info: Testacular server started at http://localhost:9876/
info (launcher): Starting browser Chrome
error (launcher): Cannot start Chrome
execvp(): No such file or directory
info (launcher): Trying to start Chrome again.
error (launcher): Cannot start Chrome
execvp(): No such file or directory
info (launcher): Trying to start Chrome again.
error (launcher): Cannot start Chrome
execvp(): No such file or directory
When I search for the problem, there are similar users that have this problem but they are using Windows. I am using Linux Mint.
It is just a small problem in config files' list of browsers. You should change the name of the browser in the configuration files under config/ directory: config/testacular.conf.js and testacular-e2e.conf.js.
If you are using chromium browser set the list of browsers to 'chromium-browse', instead of 'Chrome' like this.:
browsers = ['chromium-browser'];
Here is an ss of my testacular.conf.js file: .
If you would like to include more than one browser for you tests you can add the name of the other browsers installed in your system:
browsers = ['chromium-browser', 'firefox'];
If you are not sure about the name of your chrome browser this should help in the terminal:
ls /usr/bin/ | grep -i chrom

Categories