This category contains all my posts about software development. Tutorials, solutions to problems I’ve met, interesting things I’ve stumbled over, code samples, stuff I don’t want to forget, et cetera.
As usual, keep having to google this, so finally writing it down here…
Simply do git reset HEAD~ and make new commits as needed.
git rebase -i main), and change the commit from pick to edit.git reset HEAD~.git rebase --continueTesting your web projects with a screen reader is quite important and informative, but can also be quite annoying while jumping back and forth between developing and testing. Here are some shortcuts I keep forgetting to make NVDA a bit less annoying during development:
| Ctrl | Stops current reading |
|---|---|
| Ins + S | Switches between off-, sound-, and speech-mode (while stuff keeps being listed in log and braille view |
| Ins + Q | Quite NVDA |
Experienced getting fatal build errors on our build server during ESLint linting of our React project:
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed – JavaScript heap out of memory
<--- Last few GCs --->
[10012:0000000001DA2080] 184320 ms: Mark-sweep 2035.1 (2051.8) -> 2034.3 (2051.8) MB, 2297.9 / 0.0 ms (average mu = 0.114, current mu = 0.001) allocation failure scavenge might not succeed
[10012:0000000001DA2080] 185393 ms: Mark-sweep 2035.3 (2051.8) -> 2033.6 (2051.8) MB, 1068.8 / 0.0 ms (average mu = 0.077, current mu = 0.003) allocation failure scavenge might not succeed
The MB values looked very suspicious in that they were on either side of 2048 MB (2 GB), so suspected our project had run into some sort of limit. And seems there is indeed a max limit of ~2 GB by default on the heap size.
To increase the node heap size limit, set the --max-old-space-size to something more than 2048, e.g. like this on Windows:
To verify that it actually works (or check what it is by default), this command seems to do it:
Note that the output for some reason always seem to be a bit more than what’s set as the limit. Not sure what that’s about, but anyways… ???????
For debugging it’s often useful to do console.log(someObjectOrArray). However, if the array is long or the object deep, a lot will be truncated. Apparently there’s a util one can use to get a bit more control over this though:
Sorting strings naturally/numerically in Javascript is very simple. You just need to remember the existence of the Intl.Collator… which I keep forgetting…
You simply create one and use its compare function: