In this post we will discuss some options you have with calling async functions in constructor of your TypeScript classes.

So, first of all – why would you do this? Well, maybe you need some data from a web API to fill the object with data, or you need some input from user, or some API in code from a colleague is async. Reasons may vary, but the problem is still the same :
in TypeScript, you can’t have await statement in constructor, because constructor returns instance of object, not Promise<yourObjectType>. (All of this indeed is tied to current version of TypeScript 2.2. maybe in future with native async/await keywords in JS, things will change).

So, possible solutions depend on what happens in your async functions and if you need results from this call / calls at the time you return the object.

Solutions :

1. Try to avoid async stuff in constructor. As said earlier, constructor is a function, that should initiate the object in some way and return it immediately, not return a promise that has to be awaited. That is considered a bad practice and TypeScript doesn’t allow this. More on this problem here

http://stackoverflow.com/questions/11856778/asynchronous-constructor

http://stackoverflow.com/questions/24398699/is-it-bad-practice-to-have-a-constructor-function-return-a-promise

http://stackoverflow.com/questions/36363278/does-async-await-will-allow-us-to-be-used-on-constructors

So in some sense, need for async stuff in your constructor might be considered code smell, you are doing too much in constructor. Refactor your code.

2. If you want your async code to stay in constructor for some reason, do you need results from async calls? If not and you want to call them and let them just execute, you might consider calling async functions without await. In this way you will unfortunately be unable to receive (await) the result from these calls (values passed back via resolve).
Please note, that this might result in some non deterministic issues because of how JS handles async code and I really don’t recommend this. Also another downside is, that if you would wrap everything inside constructor with try, promises that would be rejected (analogy with throwing exception in async sense will be not caught but become unhandled exceptions).

Your constructor might then look like this :

<br />
class SomeClass1 {<br />
  constructor() {<br />
    getConfirmAsync(&quot;1 - 1&quot;);<br />
    getConfirmAsync(&quot;1 - 2&quot;);<br />
    getConfirmAsync(&quot;1 - 3&quot;);<br />
  }<br />
}<br />

Sample with try/catch block might look like this :

<br />
class SomeClass2 {<br />
  constructor() {<br />
   try {<br />
     delayAsync(3000);<br />
     delayAsync(2000);<br />
     delayAsync(1000);<br />
   } catch (e) {<br />
     console.log(e);<br />
   }<br />
  }<br />
}<br />

No awaits means that code will continue to run and your constructor will finish and hand over new instance of your class sooner than code triggered from constructor will finish its execution. Scary, right? Don’t do it!!!!

Another take on this same approach is to leave an async self executing function in constructor like this :

<br />
class SomeClass3 {<br />
  constructor() {<br />
    console.log(&quot;SomeClass3 - entry&quot;);<br />
      (async () =&gt; {<br />
        try {<br />
          await delayAsync(3000);<br />
          await delayAsync(1000);<br />
          await delayAsync(2000);<br />
        } catch (e) {<br />
          console.log(`catch triggered with exception ${e}`);<br />
        }<br />
      })();<br />
      console.log(&quot;SomeClass3 - exit&quot;);<br />
  }<br />
}<br />

Again, object would return from constructor but it would still lack calls to all async functions but this time, with proper async function, await and try/catch will work. So if for some reason first function would throw, all the others will not be hit (you can try to change the first call from 3000 to 2999 and see the results). Again, this is not recommended!

3. Simple “factory” function :

This is a way you might potentially want to go because it’s the safest one. All calls will be awaited and instance of you class will be in the state it should be.
All logic from constructor would have to be removed and stored in function that will have the logic of preparing object to the right shape. But, it is OK to separate the logic of creation from class to different function/files that knows what to do to make the object “right”?
Also you might want for safety reasons to “hide” somehow the class itself to prevent from instantiation without the factory function.
This could be done by exporting (from module) only interface of the object and “factory” function and not the class itself. Downside is, that all functions that are called in “factory” function need to be also public because “factory” function is not inside the class itself, but it is a separate function.

<br />
//exporting interface so we can work with the object outside<br />
export interface ISomeClass {<br />
	stringPublic: string;<br />
	numberPublic: number;<br />
}</p>
<p>//not exported = not visible<br />
class SomeClass implements ISomeClass {<br />
	public stringPublic: string;<br />
	public numberPublic: number;</p>
<p>	private somePrivateFn() {<br />
		console.log(&quot;this is private fn&quot;);<br />
	}<br />
}</p>
<p>export async function createSomeClassAsync(): Promise&lt;SomeClass&gt; {<br />
	let res = new SomeClass();</p>
<p>	await delayAsync(1000);<br />
	await getConfirmAsync(&quot;1&quot;);<br />
	await delayAsync(3000);<br />
	await getConfirmAsync(&quot;2&quot;);<br />
	await delayAsync(2000);<br />
	res.numberPublic = 1;<br />
	res.stringPublic = &quot;aa&quot;;<br />
	// res.somePrivateFn(); since we are not inside function this would fail</p>
<p>	return res;<br />
}<br />

This is TS that has export and import statements, but in my examples on GitHub I have this implemented without export and import. I can make a sample for you that is using modules (like the one above) but I decides to cut complexity for my readers and not use any bundling tool like webpack or browserify (I recommend webpack over browserify but that is just a matter of taste).
5. You want to hook a browser event inside the constructor , like some ready event or some other that will trigger some async functions once it happened.

Your constructor might look like this :

<br />
function ready(fn) {<br />
    if (document.readyState !== &quot;loading&quot;) {<br />
        fn();<br />
    } else {<br />
        document.addEventListener(&quot;DOMContentLoaded&quot;, fn);<br />
    }<br />
}</p>
<p>class SomeClass {<br />
    constructor() {<br />
        console.log(&quot;SomeClass5 - entry&quot;);<br />
        ready(async () =&gt; {<br />
            try {<br />
                await delayAsync(3000);<br />
                await delayAsync(1000);<br />
                await delayAsync(2000);<br />
            } catch (e) {<br />
                console.log(`catch triggered with exception ${e}`);<br />
            }<br />
        });<br />
        console.log(&quot;SomeClass5 - exit&quot;);<br />
    }<br />
}<br />

I am using a helper function from http://youmightnotneedjquery.com/ to avoid adding jQ to the project, but you get the point.

If my samples doesn’t make sense for you, please to to my GitHub repo, you can find all the code I made as examples can be found there : https://github.com/rostacik/asyncTsCtorSolutions .

If  you have TypeScript installed as global npm package, just type

<br />
tsc<br />

in the root. If you dont have TypeScript installed, you just need to do to install npm packages :

<br />
npm install<br />

and run TypeScript compiler to build all .ts files :

<br />
 &quot;node_modules/.bin/tsc.cmd&quot;<br />

Feel free to ask or discuss in the comments :)