By default
loadScript does load each file in it's own scope, so if you're relying on a shared variable scope it most likely will not work. If you really need to share scope between files you'd most likely have to use
window.* globals.
Stepping back for a second though, why do you want to avoid concatenating your JS files? I understand the desire to swap out individual modules to try things out in development, but if you are using any of the popular tools for managing JS modules & concatenating/packaging/etc. they should theoretically allow you to do a convenient swap of a module on your machine while developing. On the production side (i.e. when you actually ship your code to users), I highly recommend considering concatenation if you aren't already doing so. Each additional JS file you load carries an extra performance cost, and depending on how many files you're loading that cost could be significant.