How to run a project on nuxt.js?

Question

Node.js

Good afternoon.
I say right away: my experience in developing on node.js is zero.
I was instructed to install a project from a github that works on node.js, vue.js, nuxt.js.
I manage to start the project, but after I switch to localhost:3000 - (if you look at the process statistics) - the server starts eating up all the RAM, and as soon as it runs out - the server crashes, I don't think that 2500 gigs of RAM is not enough for it , since the developer said that his project uses about 800MB of RAM, and no problems. By the way, the developer is Western.
Here are the errors:

<--- Last few GCs --->

[10088:000001CB75D4D1D0]   108952 ms: Mark-sweep 2497.6 (2544.1) -> 2497.2 (2544.6) MB, 1903.4 / 1.0 ms  (average mu = 0.122, current mu = 0.012) allocation failure scavenge might not succeed
[10088:000001CB75D4D1D0]   111768 ms: Mark-sweep 2498.2 (2544.6) -> 2497.7 (2545.1) MB, 2786.6 / 0.6 ms  (average mu = 0.058, current mu = 0.010) allocation failure scavenge might not succeed


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 000002A82ADDC5C1]
Security context: 0x02546401e6e1 <JSObject>
    1: RegExp(aka RegExp) [00000254640082D9](this=0x024d7fc026f1 <undefined>,0x02a9741287d1 <Very long string[17268]>,0x01c979206101 <String[1]: i>)
    2: compile(aka compile) [000001EB9FE088A1] [c:\node\node_modules\linkify-it\index.js:~150] [pc=000002A82B07150D](this=0x024d7fc026f1 <undefined>,self=0x02a974125901 <LinkifyIt map = 00000382BC39C7C9>)
    ...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF758FFECF5
 2: 00007FF758FD81A6
 3: 00007FF758FD8BB0
 4: 00007FF759269AAE
 5: 00007FF7592699DF
 6: 00007FF7597A7724
 7: 00007FF75979DE87
 8: 00007FF75979C3FC
 9: 00007FF7597A5377
10: 00007FF7597A53F6
11: 00007FF75934813B
12: 00007FF75934AC3D
13: 00007FF759585D3F
14: 00007FF7595860C8
15: 00007FF759585F54
16: 00007FF75940BAD8
17: 000002A82ADDC5C1
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] start: `node --max-old-space-size=2500 node_modules/nuxt/bin/nuxt.js start`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the [email protected] start 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\Дмитрий\AppData\Roaming\npm-cache\_logs\2018-12-11T11_57_17_286Z-debug.log

And here is the full log

Log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;c:\node\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\Дмитрий\AppData\Local\Microsoft\WindowsApps;C:\adb;C:\Program Files\Git\cmd;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\nodejs\;C:\Users\Дмитрий\AppData\Local\Microsoft\WindowsApps;C:\Users\Дмитрий\AppData\Roaming\npm
9 verbose lifecycle [email protected]~start: CWD: c:\node
10 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'nuxt start' ]
11 silly lifecycle [email protected]~start: Returned: code: 134  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `nuxt start`
13 verbose stack Exit status 134
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:962:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid [email protected]
15 verbose cwd c:\node
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start"
18 verbose node v10.14.1
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 134
22 error [email protected] start: `nuxt start`
22 error Exit status 134
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 134, true ]