Closed danny-andrews closed 8 years ago
Yeah, all because of the escope
package which can't work with babel AST :/
Ah, bummer. So this is a known issue then?
Yeah, bunch of issues with inability of escope
to work with circular structures :/
I think its related to multiple version of escope/estraverse (the same issue in eslint/babel-eslint). https://github.com/babel/babel-eslint/pull/209, https://github.com/eslint/eslint/issues/4485, some others? I haven't updated babel-jscs at all so need to port over babel-eslint changes
Basically, if parser generates AST with circular refs escope
will go down, but the sad part is, no one of the maintainers of that package is interesting in fixing it :/
parser generates AST with circular refs
- abstract syntax tree (AST): "a tree representation of the abstract syntactic structure of source code"
- tree: "an undirected graph in which any two vertices are connected by exactly one path. In other words, any connected graph without simple cycles is a tree."
https://github.com/estree/estree is cycle-free for good reason.
There are underscored properties like _paths
which could do that (info on scopes, parent/child, etc)
@gibson042 sure, but we don't parse ourselves @hzoo underscore is meaningless :/
At this point only major and CST related bugs will be fixed.
Every time I run jscs against a file which has an es6 with a constructor that calls super, it chokes. .jscsrc:
src/example.js:
Example error message
Note, if I comment out the call to super in the constructor, everything works as expected.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.