| <!DOCTYPE html> | |
| <html ⚡> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>The Life and Times of a Node.js Release</title> | |
| <link rel="canonical" href="https://slides.com/danielleadams/nodejs-release-nodeconf-eu-2022" /> | |
| <meta name="viewport" content="width=device-width" /> | |
| <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation: |
Here are Jest unit tests in Node.js JavaScript to prove the normalizeString()
function's effects:
const normalizeString = (str) => str.split('').join('|').replaceAll('|', '');
test('Handles unicode joiner characters', () => {
const str = 'hello' + '\u00A0' + 'world'; // non-breaking space
const result = normalizeString(str);
expect(result).toBe('helloworld'); // Space possibly disturbed
Here are a couple niche cases where the normalizeString() function could have
an effect due to re-tokenizing the string:
Unicode joiner/non-breaking space characters: These "invisible" characters are meant to join or provide spaces between characters without breaking lines or strings. Re-splitting and re-joining a string containing them could disrupt their spacing effect. For example:
| #!/usr/bin/env bash | |
| # To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error | |
| # Make sure that the .gnupg directory and its contents is accessibile by your user. | |
| chown -R $(whoami) ~/.gnupg/ | |
| # Also correct the permissions and access rights on the directory | |
| chmod 600 ~/.gnupg/* | |
| chmod 700 ~/.gnupg |
From a Web Performance perspective, I would probably suggest simply using the Unicode symbols for these:
| rendered | keyword | HTML entity |
|---|---|---|
| ⓘ | note |
ⓘ |
| ⚠︎ | warning |
⚠︎[^1] |
| ⓧ | danger / error |
ⓧ |
| /* style-darkmode */ | |
| @media (prefers-color-scheme: dark) { | |
| :root { | |
| --text: #ddd; | |
| --bg: black; | |
| --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E"); | |
| --logo-bg: #1a5e9a; |
| #!/usr/bin/fish | |
| #/gap.fish | |
| # Apply a patch from GitHub URL. | |
| # usage: gap <url> | |
| # https://twitter.com/targos89/status/1258779153052184579 | |
| function gap | |
| curl -L "$argv[1].patch" | git am -3 | |
| end |
| Logical | Physical |
|---|---|
| Relation (Entity) | Table |
| Unique identifier | Primary key |
| Attribute | Column |
| Tuple | Row |