asset.addURLDependency, incorrect package.json fix

[DeMoorJasper]

closes #787

Less drastic alternative than #891, although this is slightly slower.

[devongovett]

Ah, good catch! Seems like this would be solved by just not using the package name in generateBundleName. Not sure we really need that anyway with #872. That way we don't need to do a resolve call in addURLDependency. WDYT?

[DeMoorJasper]

@devongovett Isn't it still necessary for that RFC?

We also support the -o or --out-file CLI option, which would override the default name for the entry file. If not provided, and the entry file matches main in package.json, use the package name.

If i'm mistaken it could still be used as a temporary patch untill the RFC gets into implementation phase I guess.

[devongovett]

Yeah, but actually not sure how useful that will be if we are hashing things anyway. Closing this one, should be fixed by #934.