A paragraph.
Profound.
<html> | |
<head> | |
<title>Font-awesome icons as characters</title> | |
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css"> | |
<style> | |
* { | |
font-family: Helvetica, Arial, sans-serif; | |
} |
import React from 'react'; | |
interface FromTo { | |
// eslint-disable-next-line @typescript-eslint/no-explicit-any | |
from: any; | |
// eslint-disable-next-line @typescript-eslint/no-explicit-any | |
to: any; | |
} | |
type Changes = Record<string, FromTo>; |
I've worked on a wide variety of node-based repositories in many organisations, and one of the questions that keeps coming up is this:
How do we effectively keep our node packages up to date?
After trying several different ways, I have recently come across a solution I have found really effective.
Defining the version of node used in a node-based repository can be a task that is overlooked.
On a few occasions, I have come across a scenario similar to the following: