question-mark
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.

"ng update" doesn't support private repos such as FontAwesome 5 Pro

See original GitHub issue

Versions

Angular CLI: 6.0.0
Node: 9.11.1
OS: darwin x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

  • Add dependency on a private repo such as FontAwesome 5 Pro
  • Run ng update @angular/core

Observed behavior

Not found : @fortawesome/pro-regular-svg-icons

Mention any other details that might be useful (optional)

This works fine using npm directly because the private repo has already been registered with npm

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:114
  • Comments:172 (45 by maintainers)

github_iconTop GitHub Comments

41reactions
Timebuttcommented, May 4, 2018

There is definitely a problem when using a private npm repository. I could only run ng update correctly once I removed my .npmrc file, and removed every private package from package.json. After running ng update @angular/cli' it finally correctly generated the angular.json file and I readded all the references I removed before.

22reactions
tilowestermanncommented, Jul 30, 2018

@hansl & @filipesilva This thread still has the “need more info” and “low frequency” labels. Based on the thread’s activity, I assume that both are not valid anymore and possibly give a false impression of the severity of this issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Angular Upgrade From 5 to 6: asset path must start with the ...
Thought I was going insane. I want to keep assets outside the main project setup under git vc, so I can have a...
Read more >
Upgrading an Application to Angular 6: Step By Step - Blog
Note that there are some other options you can pass to ng update which ... doesn't yet support private npm repos such as...
Read more >
Use Package Managers | Font Awesome Docs
Access to the Pro packages, which contain more icons and styles, requires you to configure the @fortawesome scope to use our Pro NPM...
Read more >
Bug listing with status UNCONFIRMED as at 2022/12/24 17 ...
src/plugins/quota/rquota.h: No such file or directory" status:UNCONFIRMED ... Bug:415931 - "app-admin/gkrellm patch for ATI radeon temperature support" ...
Read more >
The pfSense Documentation
software, such as “Fred's Firewall software is derived from the pfSense CE ... Fixed: DNS resolver does not update its configuration or reload...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found