Got an interesting issue for #regexp-tree: https://github.com/DmitrySoshnikov/regexp-tree/issues/179 … Let me know if you like source code transformation, compilers/transpilers, unicode, regexp, and would like to work on it.
+1 In fact, it would be great if all transforms were separate packages/plugins. Similar to Babel!
-
-
Yeah, this is something I was thinking about. Extracting interpreter, all compat-transpiler transforms, etc into own modules. The management for users though becomes more verbose to setup all this thing.
-
I think similar to Babel's approach with mono-repo could work for this. As an experiment we can work on this Unicode plugin as a separate package, and then will port everything else into its own package.
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
on this issue. I have contributed to Babel and an ESLint plugin before and fans of Unicode things. I am comfortable on code transformer but I am new to RegExp and Automata. I would be great if you could mentor me on the design phase.