lib: fixup incorrect argument order in assertEncoding

PR-URL: #57177 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>

Author: jasnell

lib/internal/fs/utils.js

@@ -154,7 +154,7 @@ function lazyLoadFs(){
 functionassertEncoding(encoding){
 if(encoding&&!Buffer.isEncoding(encoding)){
 constreason='is invalid encoding';
-thrownewERR_INVALID_ARG_VALUE(encoding,'encoding',reason);
+thrownewERR_INVALID_ARG_VALUE('encoding',encoding,reason);
 }
 }
 

test/parallel/test-fs-internal-assertencoding.js

@@ -0,0 +1,15 @@
+'use strict';
+
+// Tests to verify that a correctly formatted invalid encoding error
+// is thrown. Originally the internal assertEncoding utility was
+// reversing the arguments when constructing the ERR_INVALID_ARG_VALUE
+// error.
+
+require('../common');
+const{ opendirSync }=require('node:fs');
+const{ throws }=require('node:assert');
+
+throws(()=>opendirSync('.',{encoding: 'no'}),{
+code: 'ERR_INVALID_ARG_VALUE',
+message: 'The argument \'encoding\' is invalid encoding. Received \'no\'',
+});