Fixed an issue with unnamed module imports

When generating the array of setters you have to make sure that an import is being imported to a local binding before adding it to the array.

```javascript
import "my-module";
```
The above should not produce a setter function or attempt to reference a setter function in the meta object returned by the phase1 function wrapper.
If no setter will exist we need to still put something into the array to
keep the index matching correct with the deps array.
On Jul 31, 2014 12:40 AM, "Caridy Patino" <notifications@github.com> wrote:

> In index.js:
>
> > -      importedModuleIdentifiers.push(b.identifier(sourceModule.id));
> > +
> > +      // import "foo"; will never have a local binding name or a setter function
> > +      var localBindingIdentifier;
> > +      declarations.names.some(function(name) {
> > +        var importDeclaration = declarations.findSpecifierByName(name),
> > +          node = importDeclaration.declaration.node;
> > +
> > +        if((node && node.source && node.source.value && mod.getModule(node.source.value)) === sourceModule) {
> > +          localBindingIdentifier = sourceModule.id;
> > +          return true;
> > +        }
> > +      });
> > +
> > +      // If there is no local binding name then add a null to the setters array
> > +      importedModuleIdentifiers.push(b.identifier(localBindingIdentifier || "null"));
>
> what is this null string?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/caridy/es6-module-transpiler-system-formatter/pull/4/files#r15625993>
> .
>