Closed aredridel closed 8 years ago
that's weird, I was not able to reproduce this. can you try npm cache clean esformatter babel-runtime
and install esformatter
again?
can't repro and nobody else reported this, so I'm going to close it as invalid.
PS: I'm also going to change the way the parser is loaded soon, so it might actually help to solve this issue (see #440)
Alright. might also have been an npm bug in one of the older 3.x series.
When I upgrade from 0.8 to 0.9.3, I get this when I try to run esformatter: