Accessing Files present in ${System.DefaultWorkingDirectory} from external node script - Build Pipeline

[Imran109]

With the Release notes generator creating an HTML file, is there a way we could access the content of this HTML file.
So the HTML file that is generated is residing in the path home/vsts/work/1/s/inline.html. Once the HTML file is created, a node file is invoked by

 - script: |
$(node script/Main.js)

Is there any way to access this generated HTML file from the external node script which is called. I have a use case where I need access to the content of the file and I cannot use any external NPM package.

So far, I tried using readFileSync by passing the path

    const  readFileSync = require('fs').readFileSync;
    const html = readFileSync('home/vsts/work/1/s/inline.html')

For which I am getting the error in the build:

    internal/fs/utils.js:332
    throw err;
    ^

    Error: ENOENT: no such file or directory, open 'home/vsts/work/1/s/inline.html'
        at Object.openSync (fs.js:497:3)
        at readFileSync (fs.js:393:35)
        at Object.<anonymous> (/home/vsts/work/1/s/script/SendEmail.js:4:14)
        at Module._compile (internal/modules/cjs/loader.js:1085:14)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
        at Module.load (internal/modules/cjs/loader.js:950:32)
        at Function.Module._load (internal/modules/cjs/loader.js:790:12)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47 {
    errno: -2,
    syscall: 'open',
    code: 'ENOENT',
    path: 'home/vsts/work/1/s/inline.html'
    }

Version: Generate Release Notes (Crossplatform) 3.71.3 (Latest)

[Imran109]

Actually I figured out the issue

It was having the final output file as outputfile: '$(System.DefaultWorkingDirectory)\inline.html'
And I changed it to outputfile: '$(System.DefaultWorkingDirectory)/inline.html'

Below is the final working script

const html = fs.readFileSync(path.resolve(__dirname, './inline.html'),'utf8');