Dan Lynch

great! will be much cleaner for devs to use this way, while still giving the flags/info needed to ensure uniqueness.

I totally support this. We could add many utilities this way as well! e.g. some TS tooling to parse, lint, etc.

+1 for more generalization instead of specific to a single vendor — this is good.

any updates on this? @bcherny could you point to a place in the code where one can look to begin a PR?

@janewang thanks, what is NAJ? This is posted in the repo mentioned, here. Would be great if you can provide some insights or information. Thanks!

it's just javascript, which is how react native works. so definitely 100% yes. There's nothing this library needs to add in order to support react native. Just npm install it...

Try this, (caveat, I don't use asciimath) ```javascript const defaultOptions = { showProcessingMessages: false, messageStyle: 'none', showMathMenu: false, tex2jax: { processEnvironments: true, inlineMath: [['$', '$'], ['\\(', '\\)']], displayMath: [['$$', '$$'],...

@SamyPesse is there a way to reopen the original issue (https://github.com/SamyPesse/react-mathjax/issues/4)? I personally don't want to use the MathJax.Node, I think it's too granular to type for every equation, as...

I would encourage the use of source maps vs. expecting babel to allow customization of whitespace: https://github.com/evanw/node-source-map-support https://github.com/chocolateboy/babel-plugin-source-map-support If you integrate source maps correctly, all debugging should theoretically use the...

also, looking more deeply into the original babel issue I found a linked issue that helped me find this library: https://github.com/js-cst-tokens/cst-tokens they are not using ASTs, but rather, CSTs which...