Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is es2015 not included? #21

Open
ryan-nauman opened this issue Aug 10, 2016 · 3 comments
Open

Is es2015 not included? #21

ryan-nauman opened this issue Aug 10, 2016 · 3 comments

Comments

@ryan-nauman
Copy link

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

@basarat
Copy link
Member

basarat commented Aug 10, 2016

Plausable. I've moved on to https://github.com/basarat/byots : using it for http://alm.tools/ and will migrate atom-typescript to that as well when I get some time 🌹

@chriscoyier
Copy link

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.

@basarat
Copy link
Member

basarat commented Dec 29, 2016

. 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 🌹

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants