In "fs.copyFile(src, dest[, mode], callback)" , for callback,'err' is not defined.

[Vikranthraosb]

Affected URL(s)

https://nodejs.org/docs/latest/api/fs.html#fscopyfilesrc-dest-mode-callback

Description of the problem

There should be an "err" in the callback function for copyFile model, which is absent. Please do add it..

[avivkeller]

import { copyFile, constants } from 'node:fs';

function callback(err) {
  if (err) throw err;
  console.log('source.txt was copied to destination.txt');
}

// destination.txt will be created or overwritten by default.
copyFile('source.txt', 'destination.txt', callback);

// By using COPYFILE_EXCL, the operation will fail if destination.txt exists.
copyFile('source.txt', 'destination.txt', constants.COPYFILE_EXCL, callback); 

The documentation mentions an err argument in the callback demo code, but no where else in the docs, CC @nodejs/fs

[F3n67u]

From my test, fs.copyFile's callback has a err param.

$ node test.mjs 
file:///test.mjs:4
  if (err) throw err;
           ^

[Error: ENOENT: no such file or directory, copyfile 'source.txt' -> 'destination.txt'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: 'source.txt',
  dest: 'destination.txt'
}

Node.js v22.2.0


$ cat test.mjs                                                                
import { copyFile } from 'node:fs';

function callback(err) {
  if (err) throw err;
  console.log('source.txt was copied to destination.txt');
}

// destination.txt will be created or overwritten by default.
copyFile('source.txt', 'destination.txt', callback);

[avivkeller]

I ran the same code and got the same result, this seems like a doc-only issue. @Vikranthraosb is that was you were referring to?

[Vikranthraosb]

yes. it's an doc-only issue.

[F3n67u]

yes. it's not an doc-only issue.

If it's not an doc-only issue, could you please clarify what exactly the issue is?

[avivkeller]

Fixed by #53234