TypeScript 6.0 is a transition release bridging 5.9 and the forthcoming 7.0 (a native Go port). Most changes are new defaults and deprecations preparing for 7.0. Here is what you need to do:
Most projects need these tsconfig changes:
TypeScript 6.0 is a transition release bridging 5.9 and the forthcoming 7.0 (a native Go port). Most changes are new defaults and deprecations preparing for 7.0. Here is what you need to do:
Most projects need these tsconfig changes:
| // Slightly modified version of: https://github.com/es-shims/RegExp.escape/blob/main/test/tests.js | |
| import test from 'node:test'; | |
| import assert from 'node:assert/strict'; | |
| import {regExpEscape as escape} from './regexp-escape.mjs'; | |
| const forEach = (arrayLike, callback) => Array.prototype.forEach.call(arrayLike, callback); | |
| const inspect = String; | |
| test('strings', function (st) { |
Actually, more like hall of shame because I cannot watch/listen to myself without cringe, but in this time and age everyone has to be a salesman. Well, not really, but it kind of help with self-development and getting confidence, so whatever. Remember kids! You don't have to be competent to be a public speaker! (Or write a book. Or blog. Or OSS. Or get a job.)
Fibers are an abstraction over sequential computation, similar to threads but at a higher level. There are two ways to think about this model: by example, and abstractly from first principles. We'll start with the example.
(credit here is very much due to Fabio Labella, who's incredible Scala World talk describes these ideas far better than I can)
Consider the following three functions
| git config --global alias.br "for-each-ref --sort=committerdate refs/heads/ --format='%(HEAD) %(color:yellow)%(refname:short)%(color:reset) - %(color:red)%(objectname:short)%(color:reset) - %(contents:subject) - %(authorname) (%(color:green)%(committerdate:relative)%(color:reset))'" |
| #!/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 |
| # Terminology | |
| their_username = the GitHub username of the contributor who submitted the PR | |
| their_branch = the name of the branch they used to submit the PR | |
| repo_name = the name of your GitHub repository | |
| # First add their fork as a remote | |
| git remote add $their_username git@github.com:${their_username}/${repo_name}.git | |
| # Then fetch it | |
| git fetch $their_username |
{ "compilerOptions": { "types": ["node"], // @types are no longer auto-discovered (see ยง1.6)