Jason Watmore's Blog
417 FOLLOWERS
Jason Watmore is a web developer in Sydney, Australia and she has been building websites and web applications since 1998. In this blog, she is focusing on Angular, React, Vue, Node, and NET Technologies. She finds it extremely rewarding to contribute to the web development community and help other developers from around the world.
Jason Watmore's Blog
2M ago
Steps to test npm package dependencies locally without publishing to npm ..read more
Jason Watmore's Blog
2M ago
A slug is typically all lower case, separated by dashes (hyphens) instead of spaces and doesn't contain any special characters ..read more
Jason Watmore's Blog
11M ago
Steps to search across all client side code in the Sources tab of Chrome dev tools. Includes all JavaScript, HTML and CSS downloaded to the browser ..read more
Jason Watmore's Blog
1y ago
The below code sample shows how to add business days to a date, excluding weekends and public holidays in any specified country and state/region ..read more
Jason Watmore's Blog
1y ago
Detailed instructions on how to setup an AWS VPC from scratch then deploy a .NET 6 API to AWS Lambda with a SQL Database on AWS RDS (Relational Database Service) and Email via AWS SES (Amazon Simple Email Service ..read more
Jason Watmore's Blog
1y ago
The thing I got stuck on was how to define the type for a ...rest parameter in a TypeScript interface ..read more
Jason Watmore's Blog
1y ago
How to build a simple user registration, login and user management (CRUD) application with Next.js 13 (App Router) and MongoDB using TypeScript ..read more
Jason Watmore's Blog
1y ago
HTML encoding simply replaces HTML special characters like angle brackets with HTML entities so they can be displayed as plain text in a web page ..read more
Jason Watmore's Blog
1y ago
I ran into a weird problem this morning that had me stumped for a few hours. One of my client components was causing Chrome to lock up and max out my CPU without giving me any error message ..read more
Jason Watmore's Blog
1y ago
Just ran into this error after updating from Node 16 to Node 18 ..read more