How to correctly link to external files (like .js) in a Neorg workspace?

[name-jerry]

My Trouble

I'm having some trouble with file links in my Neorg setup and was hoping someone could point me in the right direction.
I've found that links to other .norg files work perfectly. For example, a link like {:$/src/main:} correctly navigates to the main.norg file located in my workspace's src directory.
However, when I try to create a link to an external, non-.norg file, it doesn't work. Specifically, a link formatted as {/ $/src/main.js} does not open the main.js file.

My Use Case (Why I'm doing this):

I am currently building a full-stack project with the assistance of an AI. The AI generates specification documents and TODO lists, and I want to integrate these documents directly into my project repository for unified version control.
To achieve this, I've set up the project's root directory as a single Neorg workspace. My goal is to write my notes and specifications in .norg files and be able to seamlessly link from these notes to the actual source code files (like .js, .py, etc.) within the same project.
Here's a screenshot of my project structure to illustrate my setup:

My Questions:

My understanding is that the $ symbol represents the workspace root, which works great for .norg files. My core question is whether this logic is also supposed to apply to external files, like in {/ $/path/to/file.js}.
To be more specific:

1. Is {/ $/path/to/file.js} the correct syntax for linking to non-.norg files relative to the workspace root?
2. If this syntax is correct, is there a configuration I might be missing?
3. If this is not currently supported, are there any plans to implement this feature? Being able to link directly from my notes to source code files would be incredibly powerful for my workflow.

[avonmoll]

As far as I can tell the workspace root relativity, i.e., $, only works for norg files. The help files only show it working norg files.

[name-jerry]

Thank you for your answer. I have now switched to gf