You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run ng buildwithout minified option, I get error
{ Error: Command failed: ng build --prod --configuration=config --output-path=test --base-href=/test/
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
If build is minified – everything is ok
import Auth0Lock from 'auth0-lock'
// this code causes an error
this.lock = new Auth0Lock(
'abc',
'https://localhost:4200',
options
)
There is a discussion of similar error in angular repo, and the only solution is to increase memory. I can do it, but it's not a desired solution. I have found that Autn0Lock package causes this problem in my case, so assume something may be fixed inside of it.
By the way with ng5 or on node 12.13 everything operating ok angular/angular-cli#13734
The text was updated successfully, but these errors were encountered:
With regards to ng5, if the only thing you're changing is switching to ng8 then it suggests something about that isn't compatible. Let's wait and see the outcome of the issue you linked before acting. Could you report back here once there are some more concrete findings?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️
I have added Auth0Lock to my ng8 project and it started failing on build
If I run
ng build
without minified option, I get errorIf build is minified – everything is ok
There is a discussion of similar error in angular repo, and the only solution is to increase memory. I can do it, but it's not a desired solution. I have found that Autn0Lock package causes this problem in my case, so assume something may be fixed inside of it.
By the way with ng5 or on
node 12.13
everything operating okangular/angular-cli#13734
The text was updated successfully, but these errors were encountered: