Closed shirshak55 closed 2 years ago
Hmm, that's odd, looks like it's trying to pull the fontawesome packages from their authenticated fortawesome repo, instead of using the same package versions directly from the normal npm repo (https://www.npmjs.com/package/@fortawesome/react-fontawesome).
Not sure what's up with that, or why that would fail only with npm 8 when it works fine with older npm versions. Do you want to take a look? You're totally right, it'd be good to upgrade to the latest format.
I think we can handle the issues here separately, and that'll make it easier to get things sorted with minimal risk & changes. So first updating to the new npm & fixing that react-fontawesome issue, and then separately investigating the deprecations & any audit warnings there afterwards.
I do manually check the audit warnings & deprecations when they come up - AFAIK there's none that actually matter for our use case, so it's nothing to worry about, but it's good to do updates anyway where they're easy & low-risk.
I've now somewhat fixed this - https://github.com/httptoolkit/httptoolkit-ui/commit/41b2d969bc1a0481656436379055208f4371dc8d updates the format and the NPM version used in CI, and fixes the necessary fortawesome URLs en route.
Were there any other issues you were running into here? I think everything should work now.
Thanks, I was able to install the package but I guess there is a lot of warning. I understand a lot of them might not impact us as they are mostly related to the building but still it would be better to fix some critical vulnerabilities.
Will mark this issue was closed.
NPM Version: 8.1.0
Currently, we seem to have a lot of issues on the latest npm so maybe attempt to fix it?
From the log file