Extensibility via runJS in flows. Convention or configuration

I see a lot of potential in the runJS action, but I think it could be improved by adding configuration files or certain conventions that Wappler could pick up.

It would be great that I could predefine the myalert function in a configuration file and let wappler know what arguments are to be expected.

That way we could pick up via dropdown, autocomplete or similar our custom function and the argument table would pick the exact number of them and instead of an index # it would show the name of it so I know the amount of arguments I have to enter and where to enter them.

It would allow us to share libraries and configuration files between ourselves. Very handy also in the future for npm packages.