Scripted will try to 'discover' your AMD config by looking inside html files using some patterns.
The discovery algorithm looks for certain patterns. But the algorithm is a bit fragile in the sense that if your project doesn't match one of the patterns that we've implemented it will fail to find the configuration.
This is most likely what is happening for your project.
Are you able to provide a bit more details on your project strucuture?
Specifically, Scripted will start its discovery from an html file that loads requirejs. So to provide more specific information on why its failing on your project we'd need to know where that html file is in your project and how it loads requirejs and configures it.
If you want to see some examples of structures that work. There's some in the Scripted code-base test-resources. For example here's very basic one.
https://github.com/scripted-editor/scripted/tree/master/tests/server/test-resources/nested-web-with-scripts-folder/web-app
It has a html file called 'page.html'
loads a 'main.js' script via a 'datamain' attribute in a script tag.
If your project looks like this, it should work, if it doesn't that's a bug.
If it looks differently then its hard to say more without knowing about how you use requirejs in your project.