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.
Where does the 85 kB number come from? Per https://bundlephobia.com/result?p=regenerate-unicode-properties@8.1.0 … and https://bundlephobia.com/result?p=regenerate@1.4.0 … it's 5.1 kB (for the data) + 7.7 kB (for regenerate).
-
-
The number 85 kB comes from npm pack, so it’s gzipped but unminimized. For web user the minimized size is more relevant. Regexp-tree weighs for 24 kB, so regenerate + data would counts 50% of original size. I agree with Dmitry that we should create a separate transform module.
-
I also strongly agree FWIW, was just wondering about the numbers :) IMHO regexp-tree is a build-time tool which should not be used at runtime on the web, and so file size does not matter very much.
End of conversation
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.