When you have an iframe loading an intense amount of content (like an entire video game, in the case of https://playfeed.io), and you need you need to reuse that iframe, you need to force the iframe to free up its memory usage so the browser will garbage collect it.
tmux if the machine doesn't already have it: sudo apt install tmux.tmux.ctrl+b and then d. You should see a detached note after doing so.All done!
Add the line
auth sufficient pam_tid.so
at the top of /etc/pam.d/sudo (you will need sudo access to write to that file).
You'll need to do this after at least every OS update as that file gets overwritten in those updates.
Here's a single command you can run to accomplish this:
sudo sed -i '' '2i\
auth sufficient pam_tid.so
' /etc/pam.d/sudo
I recently adopted ESLint into my workflow and enabled fix-on-save in VS Code. I've noticed since then that sometimes massive chunks of code get deleted on save by the fixes. My current suspicion is that this is entirely to blame on the rule @typescript-eslint/no-unused-expressions. I've noticed other auto-fix issues as well, however, and will track down the culprit rules as they occur.
It is possible to leave fix-on-save enabled yet disable only the bad rules! Below is the JSON config that you will need to insert in your VS Code settings to do that. As I discover more problematic rules in the future, I'll append them below.
"eslint.codeActionsOnSave.rules": [
"!@typescript-eslint/no-unused-expressions",
"*"
],
If you're using TypeScript and ESLint in VS Code, wip files or legacy files can quickly explode into a sea of red squiggles, making it hard to know where to start or track what's going on.
I like to hone in on type errors first, since they're typically more critical (as in, type errors will often completely crash your code). I keep those as scary red squiggles and tone ESLint down a bit by changing all its squiggles to just (orange) warnings.
This is easy to do with a quick edit to your user settings JSON file (accessed via the >Preferences: Open User Settings (JSON) command in VS Code):
"eslint.rules.customizations": [
{ "rule": "*", "severity": "warn" },
]
Use {@link VarName} in JSDoc comments when referencing variables or types to get:
I assume that all the features in VS Code are driven by the TypeScript Language Server and thus are applicable to any editor that utilizes that same language server.