feat!: always set a {relativePath}

[rolandjitsu]

What kind of change does this PR introduce?

• Bug Fix
• Feature
• Refactoring
• Style
• Build
• Chore
• Documentation
• CI

Did you add tests for your changes?

• Yes, my code is well tested
• Not relevant

If relevant, did you update the documentation?

• Yes, I've updated the documentation
• Not relevant

Summary
Explain the motivation for making this change. What existing problem does the pull request solve?
Try to link to an open issue for more information.

Address #69.

Does this PR introduce a breaking change?
If this PR introduces a breaking change, please describe the impact and a migration path for existing applications.

Yes. The path will be relative when falling back to the file name:

// before
console.log(file.path)
// test.json

// after
console.log(file.path)
// ./test.json

Other information

Original PR at #70.

[coveralls]

Pull Request Test Coverage Report for Build 11612627437

Details

• 8 of 8 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 11523128423:	0.0%
Covered Lines:	92
Relevant Lines:	92

---

💛 - Coveralls

[github-actions]

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀