在内存小机器上会出现这种情况

可以分开 npm install **

实在不行就就加内存，或者 build、install 用 docker 在本地机器，服务器镜像运行

<--- Last few GCS --->
[25699:0x5a04c10]
[25699:0x5a04c10]
[25699:0x5a04c10]
98357 ms: Scavenge (reduce) 250.2 (257.6) -> 249.8 (257.9) MB, 2.4 / 0.0 ms
98366 ms:
(average mu = 0.170, current mu = 0.064) allocation failTure
Scavenge (reduce) 250.5 (257.9) ->
250.2 (258.1) MB, 2.4 / 0.0 ms
(average mu = 0.170, current mu = 0.064) allocation failure
98981 ms: Mark-sweep (reduce) 250.8 (258.1) -> 247.5 (258.1) MB602.4 / 0.0 ms (average mu = 0.156, current mu = 0.139) allocation failure scavenge might not succeed

<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0xb08e80 node: Abort() [npm install]
0xa1b70e
[npm install]
3: 0xce1890 v8::Utils: Report00MFailure(v8::internal::Isolate*,,char const*, bool) [npm install]
4: 0xce1c37 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [npm install]
5: 0xe992a5
6:0xe99d86
7: 0xea82ae
[npm install]
[npm install]
[npm install]
8: 0xea8cf0 v8:: internal::Heap::CollectGarbage(v8:: internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCa[lbackFlags) [npm install]
9: 0xeabc6e v8:: internal::Heap::AllocateRawWithRetryOrFailSlownPath(int, v8::internal::AllocationType, v8::internal::AllocationnOrigin, v8::internal::AllocationAlignment) [npm install]
10: 0xe6d1aa v8::internal::Factory::NewFillerObject(int, bool, v18: internal::AllocationType, v8::internal::AllocationOrigin) [npm install
11: 0x11e5f96 v8::internal::Runtime_AllocateInYoungGeneration(iint, unsigned long*, v8::internal::Isolate*) [npm install]
12: 0x15d9c19 [npm install]