Simplify imports with path mapping→
Your TypeScript application uses relative imports. Every time you move a file, the imports break. You've configured path mapping, and now things break in an entirely new way.
Your TypeScript application uses relative imports. Every time you move a file, the imports break. You've configured path mapping, and now things break in an entirely new way.
You need to check a date using Chai. You also need to account for the test execution time.
You need to validate the checksum of a file. Rather than Googling it for the hundredth time, you decide to write a note to self, in the hope it will stick this time.
Every ObjectId includes an embedded timestamp. No need for a separate "created at" property.
Tailwind 1.3 added the ability to specify a line-height for each font-size in your config file.
Gatsby supports TypeScript out-the-box. Unfortunately, the official solution has several shortcomings which limit its usefulness. There is a better way.
You can use JavaScript's optional chaining operator multiple times within a statement. That is useful if you need to access nested properties which may not exist.
You're using Decap CMS to manage the content of your Gatsby-powered website. The default Decap CMS preview displays every field, including metadata. That probably isn't what you want.
JSON Schema includes the multipleOf keyword. This is very useful for checking that a number is rounded to a specific number of decimal places.
You can apply a "highlighter" effect to text using background gradients.