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
This article works through the steps to update dependencies in package.json...
Andrew Fletcher
It appears that the plugin or file path is not working how it used to be on...
Andrew Fletcher
This article references some of the common commands via CLI (command-line...
Andrew Fletcher
How can you find out if the Cordova plugins have been loaded? Begin by running the command ionic infoYou will see a response similar to ❯ ionic info Ionic: Ionic CLI : 6.19.0 (/usr/local/lib/node_modules/@ionic/cli) Ionic Framework : @ionic/angular 6.1.2 @angular-devkit/build-angular : 13.3.3 @angular-devkit/schematics : 13.3.3 @angular/cli : 13.3.3 @ionic/angular-toolkit : 6.1.0 Capacitor: Capacitor CLI ...
Andrew Fletcher
Updating the Cordova plugins... there are two locations to manage the...
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 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....