Nicholas C. Zakas
Nicholas C. Zakas
FWIW, Espree will always defer to the decisions of Esprima.
Okay, so it seems like we have a general agreement that: 1. We want to define what portion of source text is being represented in the AST (define logic of...
@RReverser @michaelficarra just to make sure I'm understanding about `range` and `loc`, you're saying that we should define the range that nodes represent, but not say what the values in...
Okay, gotcha, thanks for explaining. I'll try to put together a scope statement on the README soon.
My concern with leaving off the first few steps is that it's harder for us (ESTree) to track where we are relative to each proposal's stage. The TC39 proposals list...
Sorry for the late reply, been having some health-related challenges lately. So I think we're having a disconnect about the purpose of what I'm proposing (a tracking issue). The goal...
@JLHwung can you mark conversations as resolved so we can see what’s left to discuss here? @ljharb this is being submitted to the experimental folder, so we aren’t committing forever,...
Wow, this is intriguing. I think we're trying to figure out how to move forward with spec-year versions right now, so we will follow up here once we've resolved the...
In my opinion, once an extension becomes ubiquitous, it would be nice to have in this repo (like the appendices in ECMA-262).
I don't, because everyone is doing it differently right now. For JSX, any parser that implements it is implementing the same form, so it's already a pseudo-standard.