mtasa-typescript
getting error while running build watch
`> Executing task: npm run build <
npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\Windows\System32\WindowsPowerShell\v1.0\package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Windows\System32\WindowsPowerShell\v1.0\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\knowt\AppData\Roaming\npm-cache_logs\2021-09-11T08_29_20_039Z-debug.log The terminal process "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command npm run build" terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.
Executing task: npm run build <
npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\Windows\System32\WindowsPowerShell\v1.0\package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Windows\System32\WindowsPowerShell\v1.0\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\knowt\AppData\Roaming\npm-cache_logs\2021-09-11T08_29_32_402Z-debug.log The terminal process "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command npm run build" terminated with exit code: 1.`
That's not the boilerplate error :) Seems you have wrong working directory set.
Luckly, I had the same error with VSCode and PowerShell. If you have the same case, thy to change default terminal to cmd instead of powershell (why it happens?)
