Answer: All APIs of Node.js library are aynchronous that is non-blocking. It essentially means a Node.js based server never waits for a API to return data. Server moves to next API after calling it and a notification mechanism of Events of Node.js helps server to get response from the previous API call.
Source: tutorialspoint.com
| @doc """ | |
| Renders an icon. | |
| Supports three icon libraries: | |
| - [Heroicons](https://heroicons.com) - prefixed with "hero-" | |
| - [Lucide](https://lucide.dev) - prefixed with "lucide-" | |
| - [Simple Icons](https://simpleicons.org) - prefixed with "si-" | |
| You can customize the size and colors of the icons by setting | |
| width, height, and background color classes. |
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.
EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.
I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.
Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.
Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>My Angular from Scratch</title> | |
| <style> | |
| .my-component { | |
| font-family: Arial, sans-serif; |
| // Usage: | |
| // Replace React.lazy(() => import('x')); | |
| // with retryDynamicImport(() => import('x')); | |
| import { ComponentType, lazy } from 'react'; | |
| const MAX_RETRY_COUNT = 15; | |
| const RETRY_DELAY_MS = 500; | |
| // Regex to extract the module URL from the import statement |
| let timeout = null; | |
| let requestCount = 0; | |
| let queue = []; | |
| function schedule(limit) { | |
| if (!timeout) { | |
| timeout = setTimeout(() => throttleQueue(limit), 1000) | |
| } | |
| } |
| // Tailwind plugin for forms. | |
| // Basically: https://github.com/tailwindlabs/tailwindcss-forms/blob/main/src/index.js | |
| // But with a few changes. And it's easier to maintain this way. | |
| const svgToDataUri = require("mini-svg-data-uri") | |
| const plugin = require("tailwindcss/plugin") | |
| const defaultTheme = require("tailwindcss/defaultTheme") | |
| const colors = require("tailwindcss/colors") | |
| const [baseFontSize, { lineHeight: baseLineHeight }] = | |
| defaultTheme.fontSize.base | |
| const { spacing, borderWidth, borderRadius } = defaultTheme |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
