You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I look at TypeScript's ES2015.core.d.ts I see ObjectConstructor's assign. I don't see it in the latest version of Atom's lib.d.ts though and get an error
The text was updated successfully, but these errors were encountered:
Run into the same issue. We were using this to process TypeScript at CodePen and a user had trouble with spread operators. I'm not entirely sure why we weren't just using the canonical typescript, so we switched to that to solve.
. I'm not entirely sure why we weren't just using the canonical typescript, so we switched to that to solve.
Good choice. this package was before TypeScript got nightlies. And afterwards key gain was exposing the private typings. A move to conanical typescript works if you are not using any private TypeScript API (which I do for experiments). Since then I have found better ways of managing that as well aka byots. Just haven't had the time to polish that enough to move to TypeStrong 🌹
When I look at TypeScript's ES2015.core.d.ts I see ObjectConstructor's assign. I don't see it in the latest version of Atom's lib.d.ts though and get an error
The text was updated successfully, but these errors were encountered: