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:
| #!/bin/bash | |
| # Shell script to remove old wifi connections from your Mac | |
| # save this as clean_wifi.sh | |
| # do a chmod +x clean_wifi.sh in terminal | |
| # run with a ./clean_wifi.sh | |
| echo "Fetching saved Wi-Fi networks..." | |
| # Ask for the Mac password once at the very beginning |
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:
| const PasswordView = Backbone.View.extend({ | |
| events: { | |
| 'input input': 'updatePassword' | |
| }, | |
| updatePassword(e) { | |
| const pwd = e.target.value; | |
| const reqs = [ | |
| ['8+ characters', pwd.length >= 8], | |
| ['12+ characters', pwd.length >= 12], |
The official “TypeScript Handbook” is a good reference for the language. It currently has a few holes that are filled by the release notes and GitHub pull requests (which handbook and release notes link to).
“TypeScript Deep Dive” by Basarat Ali Syed was not updated much after 2020 – e.g., it does not cover template string types. But this book is still a valuable resource.
hi, i'm daniel. i'm a 15-year-old high school junior. in my free time, i hack billion dollar companies and build cool stuff.
3 months ago, I discovered a unique 0-click deanonymization attack that allows an attacker to grab the location of any target within a 250 mile radius. With a vulnerable app installed on a target's phone (or as a background application on their laptop), an attacker can send a malicious payload and deanonymize you within seconds--and you wouldn't even know.
I'm publishing this writeup and research as a warning, especially for journalists, activists, and hackers, about this type of undetectable attack. Hundreds of applications are vulnerable, including some of the most popular apps in the world: Signal, Discord, Twitter/X, and others. Here's how it works:
By the numbers, Cloudflare is easily the most popular CDN on the market. It beats out competitors such as Sucuri, Amazon CloudFront, Akamai, and Fastly. In 2019, a major Cloudflare outage k
Ich wurde jetzt schon öfters gebeten aufzuschreiben was mir alles geholfen hat, mit der Erholung vom Postcovid anzufangen und mich so zu verbessern. Anstatt das immer wieder aufzuschreiben, mache ich jetzt lieber diesen Text. Hoffentlich ist er für euch hilfreich. Ganz wichtig vorneweg: Nur weil etwas für mich gerade mal wieder zu funktionieren scheint, heißt es nicht, dass es auch für alle anderen die unter Postcovid oder gar ME/CFS leiden funktioniert.
Kurz zu mir und meinem Krankheitsverlauf: Ich bin gerade 45 Jahre alt und männlich. Im Februar 23 hatte ich mir leider Covid eingefangen, das unauffällig verlief.
Ich fahre gerne viel Fahrrad und hatte 3 Wochen Pause gemacht, bevor ich wieder mit dem Training anfing. Meine Fitness stellte sich nur langsam teilweise wieder her. Ich machte Fortschritte und versuchte mich trotzdem im Mai an meinem ersten Bikepacking-Rennen. Nach einer sehr unbefriedigenden Leistung am ersten Tag litt ich unter meineThis guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
This gist is a simple no-brainer description of the 3 ways (actually 2.5) the Web handle events.
The declarative inline HTML event listener is mostly an indirection of DOM Level 0 events, meaning this simply uses the equivalent of tag.onclick = listener behind the scene.
click meSee the new site: https://postgresisenough.dev
{ "compilerOptions": { "types": ["node"], // @types are no longer auto-discovered (see §1.6)