<p dir="auto">I would suggest to be able to use namespaces with modules.</p>
<p dir="auto">dummy1.ts file :</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="namespace MyLib {
   export class Dummy1{
       constructor(public name:string, public surname:string) {};
   }
}"><pre class="notranslate"><code class="notranslate">namespace MyLib {
   export class Dummy1{
       constructor(public name:string, public surname:string) {};
   }
}
</code></pre></div>
<p dir="auto">dummy2.ts file :</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="namespace MyLib {
   export class Dummy2{
       constructor(public name:string, public surname:string) {};
   }
}"><pre class="notranslate"><code class="notranslate">namespace MyLib {
   export class Dummy2{
       constructor(public name:string, public surname:string) {};
   }
}
</code></pre></div>
<p dir="auto">main.ts file :</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="import {Dummy1, Dummy2} from 'mylib'
function main() {
   let dum1= new Dummy1(&quot;sds&quot;, &quot;sdsq&quot;);
   let dum2= new Dummy2(&quot;sf&quot;, &quot;sdsfd&quot;);
}"><pre class="notranslate"><code class="notranslate">import {Dummy1, Dummy2} from 'mylib'
function main() {
   let dum1= new Dummy1("sds", "sdsq");
   let dum2= new Dummy2("sf", "sdsfd");
}
</code></pre></div>
<p dir="auto">By doing this, we could directly call exported data from common namespace by just calling the namespace in the import statement.</p>
<p dir="auto">Furthermore, the code generator could generate only one mylib.js file containing the Dummy1 and Dummy2 classes with system.js convention.</p>
<p dir="auto">Opening this separate issue as suggested by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/mhegazy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/mhegazy">@mhegazy</a> in the PR mentioned below. I'm not the most informed on this issue but I am opening it because I do not want it to get lost/forgot.</p>
<p dir="auto">Quoting <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/mhegazy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/mhegazy">@mhegazy</a> here:</p>
<blockquote>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/ahejlsberg/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ahejlsberg">@ahejlsberg</a> proposed a import * from "mod" syntax to do that a while back. and in this case it would be import * from namespace. the problem here is it makes it harder to do a syntactic transformation on a single file, as the compiler needs to have the full program information to know how things should be qualified. it is something that we are looking into, i would recommend filing a new issue for this instead of having the discussion on this PR.</p>
<p dir="auto">The PR is just renaming internal modules to namespaces to avoid any confusion with ES6 modules. this is something we got feedback for regularly from customers.</p>
</blockquote>
<p dir="auto">Now that TypeScript has renamed internal modules to namespaces and has the namespace keyword (PR <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="71149919" data-permission-text="Title is private" data-url="https://github.com/microsoft/TypeScript/issues/2923" data-hovercard-type="pull_request" data-hovercard-url="/microsoft/TypeScript/pull/2923/hovercard" href="https://github.com/microsoft/TypeScript/pull/2923">#2923</a>) it would be nice to be able to import a namespace and then have access to the types defined on that namespace. Would this essentially just be a new syntax to do what <code class="notranslate">/// &lt;reference path&gt;</code> does?</p>
<p dir="auto">What are the obstacles and concerns for this feature?</p>