The error was due to unsupported Node version 12.x which doesn’t support this require statement… var promises_1 = require(“fs/promises”); but this works var promises_1 = require(“fs”).promises; This can be solved by updating the Node to the latest.
var fs = require(“fs”); var filename = “./index.html”; function start(resp) { resp.writeHead(200, { “Content-Type”: “text/html” }); fs.readFile(filename, “utf8”, function(err, data) { if (err) throw err; resp.write(data); resp.end(); }); }
It’s the directory where the node interpreter was started from (aka the current working directory), not the directory of script’s folder location (thank you robertklep). Also, current working directory can be obtained by: process.cwd() For more information, you can check out: https://nodejs.org/api/fs.html EDIT: Because you started app.js by node app.js at ExpressApp1 directory, every relative … Read more
If you use fs, be sure it’s only within getInitialProps or getServerSideProps. (anything includes server-side rendering). You may also need to create a next.config.js file with the following content to get the client bundle to build: For webpack4 module.exports = { webpack: (config, { isServer }) => { // Fixes npm packages that depend on … Read more
It looks like the glob npm package would help you. Here is an example of how to use it: File hierarchy: test ├── one.html └── test-nested └── two.html JS code: const glob = require(“glob”); var getDirectories = function (src, callback) { glob(src + ‘/**/*’, callback); }; getDirectories(‘test’, function (err, res) { if (err) { console.log(‘Error’, … Read more
A better approach, if you are just going to hook up “data” to “write()” and “close” to “end()”: // 0.3.x style fs.createReadStream(filename, { ‘bufferSize’: 4 * 1024 }).pipe(response) // 0.2.x style sys.pump(fs.createReadStream(filename, { ‘bufferSize’: 4 * 1024 }), response) The read.pipe(write) or sys.pump(read, write) approach has the benefit of also adding flow control. So, if … Read more
This is probably because you are trying to write to root of file system instead of your app directory ‘/avatar/myFile.png’ -> __dirname + ‘/avatar/myFile.png’ should do the trick, also check if folder exists. node.js won’t create parent folder for you.
Older answer with callbacks You want to use the fs.readdir function to get the directory contents and the fs.rename function to actually do the renaming. Both these functions have synchronous versions if you need to wait for them to finishing before running the code afterwards. I wrote a quick script that does what you described. … Read more
You can use the path module to join the path of the directory in which helper1.js lives to the relative path of foobar.json. This will give you the absolute path to foobar.json. var fs = require(‘fs’); var path = require(‘path’); var jsonPath = path.join(__dirname, ‘..’, ‘config’, ‘dev’, ‘foobar.json’); var jsonString = fs.readFileSync(jsonPath, ‘utf8’); This should … Read more