readdir | Recursively read a directory | Runtime Evironment library

You're correct, fs.FileInfo implement the interface fileInfo!

However, that does not mean that you can assign a value of type []fs.FileInfo to a variable typed []fileInfo - these are completely different types.

In fact - the types cannot even be converted to each other, they are laid out completely differently in memory: interface values are a pair of {concrete type,data struct pointer}, and struct values are just what you see in the struct!

So, the short answer is that you have to do something like your loop which assigns values and appends them to the slice of interface values... behind the scenes what is happening is Go is creating an interface value for each of the struct slice elements for you, automatically.

A succinct way to say this all is: "Go interfaces types are covariant with the struct types that implement them, but slices of interface values are not type-covariant with slices of structs that implement those values."

For more info on slices of structs vs. interface types, see https://www.timr.co/go-interfaces-the-tricky-parts/

Since you're having trouble following the other S.O. answer, try this. First stick the files in an array with the filemtime as the key, then use ksort to sort it before you start iterating

You need to add something like:

printf does not take an integer. It takes a format string and a variable list of arguments. Your problem can probably be fixed by changing:

(dir->d_name) !=".." is not a valid way to check if dir->d_name is equal to the string "..". You need to use strcmp(dir->d_name, "..");

The string literal ".." refers to a location in memory which contains the 3 bytes ., ., and \0. It is entirely possible for dir->d_name to also contain those same bytes, but since it is in a different place dir->d_name == ".." will be false. But strcmp(dir->d_name, "..") will evaluate to zero if the contents of the two locations are the same.

I am answering my own question, in case it helps some others like me, who are moving from frontend coding to understanding node.js.

It's difficult to grasp that some modules are just not meant for browsers and fs is one them and when you try to use 'require' that's another roadblock.. so if, like me, you are here because you tried to use fs in your javascript linked to your html to read something from your local machine or server and expected it to show up on the browser, it won't work.

It's a bit frustrating but once you get your head around it, it makes sense. So although this might not be the answer you looked for, I thought I'd just share this so that you don't waste more time, trying to make it work.

Getting to understand node.js and how to use fs on node.js would be better use of time..:-)..

Firstly you forgot to return your created nodes this is why you found the void problem, secondly, you have to use a synchronous version of readdir.

Your code is fine, make sure the path is correct. Check where the folder is in relation to where you are running the code from. Check the folder's name - make sure you don't have a typo.