Skip to main content
11
results
Andrew Fletcher
When executing the following command, the response I'm getting is npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2fpro-light-svg-icons - Not found npm ERR! 404 npm ERR! 404 '@fortawesome/pro-light-svg-icons@^5.11.2' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.This error 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2fpro-light-svg-icons - Not...
Andrew Fletcher
This article works through the steps to update dependencies in package.json...
Andrew Fletcher
Currently, I have a situation where I have two repositories.  The first is...
Andrew Fletcher
When attempting to do a git push, are you getting the following...
Andrew Fletcher
In this woalk through I am going to use GitHub.  However, the steps are...
Andrew Fletcher
Have you noticed through your Google account that there are items being indexed that shouldn't have been?   One for me was taxonomy terms.  Not important to be followed. Being indexed on my sitemap (do I just erase those entries on the XML file?) Being crawled (I am guessing this is with a robots.txt file though I have never created one before) Being viewed (stumbled upon) -> if this even possible to block?   Resolve these quickly by simply adding disallow in robots.txt...
Andrew Fletcher
I’m recently doing an IoT project. I wanted to investigate the network...
Andrew Fletcher
You would have come across a URL string that appears...
Andrew Fletcher
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
A bug bear that I have had for a while with Drupal content is how come the...
Andrew Fletcher
As a process I apply patches locally first, then using git upload the update(s) to a development site on the server.  Once the testing has been completed, the final step to apply the patch to the production site.   Using Terminal or your preferred shell program, navigate to the correct directory.  Then run this command using the name of the patch file (example.patch): patch < example.patchHowever, if you are patching Drupal core then remember to patch from the root directory...