Skip to content

Known Contribution Issues

jmarkowski edited this page Aug 19, 2020 · 3 revisions

Javascript heap out of memory

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. Our NGX libraries are being constantly developed, so environment needs more and more size to build project. In case Javascript heap out of memory exist, thing developer can do is to increase limits of Node environment by passing export NODE_OPTIONS=--max_old_space_size=8192 command. Of course exact 8192 can be changed to 4096 or 2048.

Enigmatic errors

If there are enigmatic errors, which don't specify the problem like that

12:44:47 PM: ERROR: Cannot read property 'Symbol(Symbol.iterator)' of undefined
12:44:47 PM: An unhandled exception occurred: Cannot read property 'Symbol(Symbol.iterator)' of undefined

OR:

12:44:47 PM: ERROR: Cannot read property 'toString' of undefined
12:44:47 PM: An unhandled exception occurred: Cannot read property 'toString of undefined

You should take a look at the imports of files inside library, so for example imports like

  • import { ListLinkDirective } from '@fundamental-ngx/core';, or import { ListLinkDirective } from '../../..'; can cause some unexpected behaviours and errors during compilation. It's always good to change it to direct import like that:
  • import { ListLinkDirective } from '../directives/list-link.directive'; It's only for files inside lib/ folder. Documentation side can contain imports from @fundamental-ngx/core Also import on *.scss files should not containt .css extension. So for example
  • @import "~fundamental-styles/dist/list.css"; has to be changed to @import "~fundamental-styles/dist/list";
Clone this wiki locally