search

garmeeh / local-cors-proxy

Simple proxy to bypass CORS issues.
MIT License
328 stars 81 forks source link

'lcp' is not recognized as an internal or external command... #10

Closed stepanstaniek closed 4 years ago

stepanstaniek commented 4 years ago

Hi All,

When trying to run proxy, I do receive below response. Running on VS Code on Company Windows 10 OS. Can you please suggest some solution? system variable "npm" set to ...AppData\Roaming\npm lcp installed globally as https://www.npmjs.com/package/local-cors-proxy

Thanks in an advance Stepan

> npm run proxy > fss_portal_public@0.1.0 proxy C:\Users\stanist3\FSSRepository\portal-public > lcp --proxyUrl http://X.X.X.X:8080 2020-02-16T16_22_14_228Z-debug.log

'lcp' is not recognized as an internal or external command, operable program or batch file. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! fss_portal_public@0.1.0 proxy: lcp --proxyUrl http://X.X.X.X:8080 npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the fss_portal_public@0.1.0 proxy script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\stanist3\AppData\Roaming\npm-cache_logs\2020-02-16T16_22_14_228Z-debug.log

stepanstaniek commented 4 years ago

Resolution is to install it without parameter -g as globally. npm install local-cors-proxy works now...