0
fs.writeFileSync("sam.txt","data is content"); always write proper content , dont write byte code , so it means writeFile and WriteFileSync dont care about the encoding mode.
-
noob
Jan 19 '17 04:32
1
noob
answered Nov 30 '-1 00:00
i tried something with differ type of encoding . it give same output . so is there encoding option is just need to be any string or what /.
console.log(fs.readFileSync('file.txt','utf8'));//utf8 encoding
console.log(fs.readFileSync('file.txt','binary'));//binary encoding
console.log(fs.readFileSync('file.txt','ascii'));//ascii encoding
ascii , binary , utf8 all give same output for redFileSync and readFile .
0
Mitul Dabhi
answered Nov 30 '-1 00:00
you forgot to pass encoding type which is second argument , i passed utf8 for below code so pls check it work like charm
var fs=require('fs');
fs.readFile(filePath, 'utf8', getFile );
function getFile (error, fileContent) {
if (error) return callback(error)
console.log(fileContent);
}
or
var fs=require('fs');
fileContent=fs.readFileSync(filePath, 'utf8');
readFile and readFileSync return buffer if you dont specify character encoding type .
0
Rasi
answered Nov 30 '-1 00:00
Why readFile / readFileSync return Buffer instead of file Content ?
it is intended to make it possible to work with filesystems that allow for non-UTF-8 filenames. mostly NTFS and HFS+ file systems have utf-8 file encoded.so for that one can pass encode option to 'utf-8'
how to convert Buffer to proper File content ?
1. pass encode option to utf8
fs.readFile(filePath, 'utf8', callback);
2. toString() will do conversion
fs.readFileSync(filePath).toString();