Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TS is slow when parsing elixir files.

See original GitHub issue

When i open a elixir file i get TS took 356ms to parse document, will be disabled for current file. It happens with small or larger file.

is this because i’m on a m1 mac?

Issue Analytics

State:
Created 2 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

connorlaycommented, Oct 21, 2021

Thanks for the explanation @jonatanklosko !

1reaction

jonatankloskocommented, Oct 21, 2021

Yup, I also documented that briefly here.

And even in some particular cases where I was tempted to make the AST more specific, I quickly came up with scenarios where it would break. For example the “when” operator in stab clauses could be a more specific guards node, but due to macros it can really be used anywhere and it’s hard to tell, like in match?(x when x == 1, 1) (and it would be hard to unify with defs anyway).

Top Results From Across the Web

Speed up parsing a text file - Questions / Help - Elixir Forum

I recently found String. split to be much slower than a regex for parsing lines of input. mix profile. fprof is easy to...

Processing Large CSV files with Elixir Streams - Poeticoding

But I dont have any success to perform a fast read of file. Stream seems very slow when comparing Elixir time ( about...

The 10 Most Common JavaScript Issues Developers Face

If you need help figuring out why your JavaScript isn't working, consult this list of the 10 most common JavaScript issues from a...

Moving from Webpack to esbuild on Phoenix | OpenFn/docs

Going through our webpack.config.js file I can see that it: Conditionally provide sourcemaps depending on the environment. Uses babel to parse ...

Bug listing with status RESOLVED with resolution OBSOLETE ...

systemPrefs with at least two files" status:RESOLVED resolution:OBSOLETE ... Bug:300598 - "dev-perl/XML-Parser: ebuild may silently fail with distcc" ...