I uploaded the laravel project to the host and an error came out: The file was not found in the folder: /home/login/Domains/domain/public/build/manifest.json, seems to need to be run in ssh npm run build, but when I do this:

@ builds /home/login comes out/Domains/Domain In order to build

(node:30644) unhandledpromiserejection warns: syntax error: unexpected token '||='
in Loader.moduleStrategy (internal/modules/esm/translators.js:145:18)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:30644) unhandledpromiserejection warning: Unhandled promise rejection. This error occurred either because an asynchronous function was run inside without a catch block, or because a promise was rejected that was not processed using .catch(). To terminate the node process with an unhandled promise rejection, use the CLI flag `--unhandled rejections=strict` (see .html#cli_unhandled_rejections_mode ). (identification

what do I need to write to make everything work?

I uploaded the laravel project to the host and an error came out: The file was not found in the folder: /home/login/Domains/domain/public/build/manifest.json, seems to need to be run in ssh npm run build, but when I do this:

@ builds /home/login comes out/Domains/Domain In order to build

(node:30644) unhandledpromiserejection warns: syntax error: unexpected token '||='
in Loader.moduleStrategy (internal/modules/esm/translators.js:145:18)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:30644) unhandledpromiserejection warning: Unhandled promise rejection. This error occurred either because an asynchronous function was run inside without a catch block, or because a promise was rejected that was not processed using .catch(). To terminate the node process with an unhandled promise rejection, use the CLI flag `--unhandled rejections=strict` (see https://nodejs./api/cli.html#cli_unhandled_rejections_mode ). (identification

what do I need to write to make everything work?

• laravel
• npm
• ssh

• This happened to me once before. The node version was older. I simply installed the latest version for node and did a new build for the project. I then uploaded public/build, ensured all Laravel settings and permissions. – I. Antonov Commented Mar 10 at 19:25

1 Answer 1

I think it relate to your node version. Try to upgrade it.