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
A summary of Node package commands Short cut commands npm install...
Andrew Fletcher
Goal: Restrict content access through username and password entry on an Nginx...
Andrew Fletcher
This article works through the steps to update dependencies in package.json...
Andrew Fletcher
Goal: Restrict content access through username and password entry. 1: Apache...
Andrew Fletcher
You would have come across a URL string that appears as https://example.com/project-search?search_api_fulltext=&f%5B0%5D=species%3AAtlantic%20SalmonAs you would already seen %20 many times, that is a space.  Commonly seen in file names either documents or images. However, what about the others.  Off the top do you know what %3D is?  Maybe, but I didn't.  Below is a quick guide to percentage encoding...
Andrew Fletcher
A bug bear that I have had for a while with Drupal content is how come the...
Andrew Fletcher
Core Data - customising our data model When you are using Core Data, and let's...
Andrew Fletcher
Step 1: Install Homebrew Homebrew is the missing package manager for macOS. As...
Andrew Fletcher
Working on a new CentOS 7 server, Node wasn't installed.  You can...
Andrew Fletcher
I started out with a simple task... install Tailwindcss.  What unfolded is something that many of us have experienced time and time again. For anyone that has completed this task before knows that through shell the command is # Using npm npm install tailwindcssHowever, before doing so I wanted to check the version of node on the server and in Plesk.  The shell command node -v was showing v7.10.1 whereas in Plesk v10.16.0.  Not great being a few versions behind....