Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in Powershell #23

Closed
aersam opened this issue Nov 8, 2018 · 4 comments
Closed

Error in Powershell #23

aersam opened this issue Nov 8, 2018 · 4 comments
Labels

Comments

@aersam
Copy link

aersam commented Nov 8, 2018

On Windows, in VS Code, using Powershell host, I get the following error:

npm-gui web-server running at http://localhost:1337/
{ Error: ENOENT: no such file or directory, open 'C:\SOMEPATH\�w^~)�\package.json'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.readFileSync (fs.js:551:33)
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:170880
    at Generator.next (<anonymous>)
    at z (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168409)
    at o (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168611)
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168670
    at new Promise (<anonymous>)
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168552
    at L (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:171137)
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\SOMEPATH\\�w^~)�\\package.json' }
{ Error: ENOENT: no such file or directory, open 'C:\SOMEPATH\�w^~)�\package.json'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.readFileSync (fs.js:551:33)
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168779
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168846
    at Generator.next (<anonymous>)
    at z (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168409)
    at o (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168611)
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168670
    at new Promise (<anonymous>)
    at C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:168552
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\SOMEPATH\\�w^~)�\\package.json' }
Error: [object Object]
    at ChildProcess.s.on (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:535:167021)
    at emitOne (events.js:116:13)
    at ChildProcess.emit (events.js:211:7)
    at ChildProcess.e.emit (C:\Users\ehrsam\AppData\Roaming\npm\node_modules\npm-gui\dist\server\main.js:459:62280)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:196:12)
    at onErrorNT (internal/child_process.js:372:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
@q-nick
Copy link
Owner

q-nick commented Nov 8, 2018

@aersamkull

  1. Apart from the error in the console, does the application work correctly?
  2. If you start npm-gui in folder that contains package.json - this error also appear?

@aersam
Copy link
Author

aersam commented Nov 8, 2018

I get the error only if start in the folder by using powershell. cmd works

@q-nick q-nick added the bug label Nov 8, 2018
@SampathKumar27896
Copy link

Hi, Is this bug still exists/relevant now?. I could run the application using powershell. This is my powershell version
Name Value


PSVersion 5.1.19041.1682
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.1682
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

@aersam
Copy link
Author

aersam commented Sep 8, 2022

Yes works now for me, too.

@aersam aersam closed this as completed Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants