developer resources
Codebales holds an ever growing number of solutions to problems that we have experienced in our day to day code writing
Selected filter
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
•
Visual Studio Code (VS Code) allows you to manage extensions using the VS Code...
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
•
phpcs issue in Visual Studio Code, I'm receiving this warning in VS Code:
phpcs: Unable to locate phpcs. Please add phpcs to your global path or use composer decency manager to install it in your project locally.
How to fix
You can install phpcs by using composer global command:
composer global require squizlabs/php_codesnifferThen in VS Code, go to
Click Code -> Preferences -> Settings
Select User Settings and locate 'PHP CodeSniffer', or in the Search settings enter...
Andrew Fletcher
•
In this woalk through I am going to use GitHub. However, the steps are...
Andrew Fletcher
•
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
•
Setting up a new project in Docker and VS Code.
Using Terminal, go to your...
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...