The latest articles on DEV Community by Vlatko Koudela (@vkoudela). https://dev.to/vkoudela https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F237406%2F3beaee84-c4ac-4dd9-b29a-ffa2d829e74e.jpeg https://dev.to/vkoudela en Vlatko Koudela Tue, 26 Nov 2019 21:40:43 +0000 https://dev.to/vkoudela/how-to-fix-received-invalid-response-from-npm-when-using-other-registry-in-npmrc-and-yarnrc-173f https://dev.to/vkoudela/how-to-fix-received-invalid-response-from-npm-when-using-other-registry-in-npmrc-and-yarnrc-173f <p>Working on long term projects and keeping up with the technologies can be hard. It may happen that some of the technologies you're using change their configuration setting and you don't see their docs on time or you simply - forget. This happened to me while using the pro version of FontAwesome. Their license "authentication" has changed over time and that's fine if your project is young, but it's less obvious when working on long term project.</p> <p>If you're reading this article, then you might be taken here by search engine that crawled this error:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>error Received invalid response from npm. </code></pre> </div> <p>In my case, I got this error while trying to execute <code>yarn info prop-types</code>, but it can be any package from your packages.json file.</p> <p>During the problem, <code>yarn install</code> doesn't work so you may end up with the similar looking error:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>yarn install v1.19.2 [1/4] 🔍 Resolving packages... [2/4] 🚚 Fetching packages... error An unexpected error occurred: "https://npm.example.com/prop-types/-/prop-types-15.7.2.tgz: Request failed \"404 Not Found\"". info If you think this is a bug, please open a bug report with the information provided in "/Users/vkoudela/path-to/your-project/yarn-error.log". info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. </code></pre> </div> <p>When you encounter this or similar problem, many developers would say:</p> <ol> <li>Delete <code>node_modules</code> folder and then try <code>yarn install</code> </li> <li>Delete <code>node_modules</code>, <code>yarn.lock</code> and then try again</li> <li>Run <code>yarn cache clean</code> and then try again</li> </ol> <p>But, what if you already tried that and it didn't help?</p> <p>We, developers, when trying to fix something, we tend to run something and then we see what happens. We fix one problem, then another, until we fix all of them.</p> <p>So, to be able to solve your problem, you have to know in which order <code>yarn</code> is using *rc files.</p> <ol> <li>In your project root (folder where you have your packages.json), it looks for <code>.yarnrc</code> file</li> <li>Then it looks for <code>.npmrc</code> </li> <li>Then it tries to find those files globally, which is usually your user folder: <code>~/.yarnrc</code> </li> <li>Then it tries the same thing with <code>~/.npmrc</code> </li> </ol> <p>While troubleshooting and "fixing" the problem, you have to be aware of the fact that even if <code>yarn install</code> fails to execute properly, it would still create <code>yarn.lock</code> file taking all the settings from all <code>.npmrc</code> and <code>.yarnrc</code> on all four locations on your file system. So, even if you change any of the *rc files on any location after first failed attempt, it's not enough because settings are written in <code>yarn.lock</code> and yarn will reuse them on next execution.</p> <p><strong>Therefore, don't forget to delete <code>yarn.lock</code> before every other attempt of <code>yarn install</code>.</strong></p> yarn npm