Glob file system to locate substitution variations

[m-mujica]

Closes #22

so @matthewp I have a couple of issues getting to work this:

• In production mode, steal tries to load path and glob. I added them to npmIgnore but that doesn't seem to work; here is a branch on the sample app https://github.com/m-mujica/steal-conditional-interpolation-example/tree/new-conditional, I wonder how can I prevent steal to try to load them

• I get a different error when I use relative imports, for some reason steal doesn't look for the conditionally loaded modules in the bundles folder but in dist/{module_name} https://github.com/m-mujica/steal-conditional-interpolation-example/tree/relative-import

do you see anything in the code that might be easier to approach in a different way?

[m-mujica]

I've been also thinking about the scenario where someone imports a module like

import '#{foo}';

With my current changes, we'd glob for the root project folder and the number of matches will be pretty big. I guess we can document that doing this is a bad idea, can we do better?

[m-mujica]

So, I'm trying a slightly different approach for the string interpolation

• Normalize the module name without the conditional ( if import 'foo/#{bar}', we normalize foo)
• locate the normalized name adding "/*", in our example, we'll locate({ name: "foo/*" })
• global the filesystem with the address returned in the previous step
• Iterate over the files found above ^, replace the conditional part of the module with the file name and normalize that name
• Add the normalized name variations to loader.bundle

This is working fine, I'm steal dealing with the problem of steal loading dist/glob on production mode when the app is minified, I noticed the error doesn't happen if minify is set to false.