Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERROR: Cannot read property 'unshift' of undefined

See original GitHub issue

I’m submitting a…


[ ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package


[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?

Environment


Angular version: X.Y.Z


- Node version: XX  
- Platform:  

Others:

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:12

Top GitHub Comments

8reactions

camolift29commented, Jun 27, 2019

I have resolved this problem in another thread. When you execute ng add @ng-toolkit/universal, it adds the 1.1.2 version (At least for me) so I decided to change the version to 7.1.2 which is the last version, then I deleted node_modules folder and reinstalled all dependencies with npm i. Finally I executed ng add @ng-toolkit/universal @7.1.2 and it worked

2reactions

hbk899commented, Jul 11, 2019

I have resolved this problem in another thread. When you execute ng add @ng-toolkit/universal, it adds the 1.1.2 version (At least for me) so I decided to change the version to 7.1.2 which is the last version, then I deleted node_modules folder and reinstalled all dependencies with npm i. Finally I executed ng add @ng-toolkit/universal @7.1.2 and it worked

Was this getting error unshift error again so first i did npm i @ng-toolkit/universal @7.1.2 then ng add @ng-toolkit/universal @7.1.2 and it worked for me