[BUG] Failed to read the config file error

[Maghish]

This bug occurred I tried @rage-js/core package outside testing directories for the first time and right after install, it started to spit out "Failed to read the config file" error everytime I try run, even though the rage.config.json path is given correctly. And then I checked the core package itself and ran my project with npm link from the local core package directory and somehow it worked out fine without any problem, I was very confused and unlinked the local core package and reinstalled @rage-js/core@latest again and this time it works, I don't know if this error is random or not but IF this error happens again anytime soon, please work on this issue.

Note

readConfigFile util function inside the core package merges the current path and then the given path, for example: E:/Project is the full path and ./rage.config.json is the given path and path.join will merge those two into E:/Project/rage.config.json. But there is a chance that the user will give a full path like E:/Project/rage.config.json itself as the given path and due to this, the readConfigFile will confuse and display the final path as E:/Project/E:/Project/rage.config.json. Hence this could be prevented, Somehow.

[Maghish]

Works sometimes, sometimes it doesn't. Will fix it when it shows up again

[Maghish]

Removed almost every process.cwd line of code in every RAGE repositories, but sometimes there could be errors where the user may just . or any other thing, that could potentially cause some problems when doing I/O work. At that moment, process.cwd would save the day as process.cwd + . = process.cwd so the program could know the correct path, as simply giving . is not valid a path