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
Like many devs at the moment, looking for log4j2 on your server... how to do? First I used the command find / -name log4j2.xml -type fWhich in turn produced the following results /opt/solr-8.5.2/server/resources/log4j2.xml /var/solr/log4j2.xml  Version Ok, so log4j2 exists on the server the client is using... in Solr.  How about determining the version number? The version here matters as 2.15.0 is good to go.  To find the version use sudo find / -name 'log4j*' The output of...
Andrew Fletcher
A bug bear that I have had for a while with Drupal content is how come the...
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...
Andrew Fletcher
Updating Realm and RealmSwift from 5.5.x to 10.0.0 brought in the following error  RealmSwift 10.1: framework not found realm-syncThe greatest clue I came across to solving this issue was on the Realm GitHub issues page for realm-sync error.  However, updating Cocopods wasn't the only step required to correct this issue.  The steps I took were: Update Cocopods to v1.10.0 using sudo gem install cocoapods Deintegrate all of your pods pod deintegrate Install the pods from the...