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
Hello? 6.1.1 and this is still an issue. There are no alternative ways of getting this to work at the moment, which means that we're going to have to drop angular soon.
Looks like strictSsl is actually a boolean and not a string so the if statements below won't do anything. I changed the code to this in the compiled output and it works now:
In addition, I also had to manually pass my registry even though I have it set in my environment as npm_config_registry, so I did the following after the fix above to update:
ng update --all --registry=$npm_config_registry
Reacted by Jonas Gröger
angular-automatic-lock-bot commented on Sep 8, 2019
Activity
m00k commentedon May 14, 2018
Would be useful to respect cafile property as well.
readme42 commentedon May 14, 2018
Thanks a lot :)
fix(@schematics/update): Allow usage strict SSL configuration
fix(@schematics/update): Allow usage strict SSL configuration
fix(@schematics/update): Allow usage strict SSL configuration
JonasGroeger commentedon Jun 25, 2018
Which version will this be included in?
tabinnorway commentedon Jul 31, 2018
Hello? 6.1.1 and this is still an issue. There are no alternative ways of getting this to work at the moment, which means that we're going to have to drop angular soon.
CSchulz commentedon Jul 31, 2018
It seems that there is a regression with 6.1.X.
npm updateworked for me in 6.0.8, but with 6.1.1 not any longer.elclanrs commentedon Aug 3, 2018
I tracked the issue down to schematics/update/update/npm.ts#L125-L139.
Looks like
strictSslis actually a boolean and not a string so theifstatements below won't do anything. I changed the code to this in the compiled output and it works now:In addition, I also had to manually pass my registry even though I have it set in my environment as
npm_config_registry, so I did the following after the fix above to update:ng update --all --registry=$npm_config_registryangular-automatic-lock-bot commentedon Sep 8, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.