[11:01:23] good morning/afternoon/evening everyone! [11:04:10] I'll be taking notes again [11:04:12] let's start [11:04:24] since last time [11:04:29] 2.5 was out last Friday [11:04:50] also https://www.npmjs.com/package/esprima indicates that the downloads now exceed 8M last month [11:04:57] with full ES6 support, right? [11:05:11] feature complete [11:05:14] or ES2015, even [11:05:17] woo! [11:05:25] it may have defects, or incomplete early error handling [11:05:52] right, our support at this point is representation of any valid program [11:06:20] we continue to focus on polishes for 2.6 [11:06:31] the new unified test runner from jlast has been landed [11:07:02] I already found an issue with Firefox 39: https://github.com/jquery/esprima/issues/1271 [11:07:08] more like our problem, not Firefox's problem [11:07:15] hey guys [11:07:27] morning jlast [11:07:37] looking at 1271 [11:07:53] jlast: excellent :-) [11:08:09] oh interesting. this is a really nice argument for saucelabs [11:08:12] probably just require another special handling, i.e. ignoring value check for a regex [11:08:26] true [11:08:45] there's a couple of other bugs that I'll be working on [11:09:02] And I really want to replace coveralls with codecov.io [11:10:01] jlast: if you got that fix, I want to put it https://github.com/litixsoft/karma-detect-browsers [11:10:14] works well in my WIP setup [11:10:59] cool [11:11:29] ariya, not sure if it's a priority now, but could you sketch out how you see https://github.com/jquery/esprima/issues/1176 looking [11:12:30] well now that you bring that up :-) [11:12:45] here's a controversial idea: post 2.6, I'm thinking of switching the code base to TypeScript [11:13:07] I have an experimental branch that I can publish in a week or two (just to clean-up embarassing notes here and there) [11:13:18] it goes a long way in increasing the modularity and readability [11:13:21] haha - that could be interesting [11:13:38] i could see that helping readability a lot [11:15:05] and refactoring and things like that [11:15:33] per our usual tradition, nothing will regress if we make that switch [11:15:46] sounds good. [11:16:00] we will keep the high standard for complexity, coverage, test suite, etc [11:16:10] I plan on looking into the https://github.com/jquery/esprima/issues/1048 this week [11:16:37] jlast: please do, let me know if you need some help [11:16:52] and I think https://github.com/jquery/esprima/pull/1270 looks good, I'll merge it later today [11:17:03] sure, I'll share questions on the issue [11:17:10] we'll probably not pursue https://github.com/jquery/esprima/pull/1243 further [11:17:22] per my comment on https://github.com/jquery/esprima/issues/1210 [11:18:02] agreed. i'll close the PR. they're linked anyways [11:18:35] I think we'll have an even more polished Esprima in 2.6 :-) [11:18:53] what are the goals for 2.6? [11:19:06] squash all those bugs + more tests [11:19:38] cool - i can take a look at issues once there's a milestone https://github.com/jquery/esprima/issues?q=is%3Aissue+milestone%3A2.5+is%3Aclosed [11:19:54] jlast: good point, let me create the milestone [11:20:11] as I verify our ES6 support, I also start to file issues on Espree (just to be a good citizen) [11:20:15] https://github.com/eslint/espree/issues [11:20:34] unfortunately my time is rather limited in contributing back our fixes there [11:23:05] oh BTW, the use of TypeScript means we can start using many ES6 features as well [11:23:48] that's all I have from my side [11:23:54] anybody wants to discuss any other topics? [11:25:14] I've got nothing new for here [11:25:19] just reading https://github.com/jquery/esprima/pull/1256 [11:25:48] gibson042: have you put some thought into the project I have proposed? :-) [11:26:13] yes; expect a response this week [11:26:22] sweet [11:26:24] * ariya is thrilled [11:26:52] I think that's all for this week [11:27:00] thank you everyone for your participation! [11:27:04] see you again next Wed! [11:27:05] * ariya waves