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.
-
-
Replying to @DmitrySoshnikov
Hi Dmitry, here is a hands up
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.2 replies 0 retweets 0 likes -
Replying to @DmitrySoshnikov @JLHwung
I’m really hoping we can find a way to share commonalities (like the raw Unicode data) between regexpu-core and your implementation, so they can easily be updated at the same time. I’m worried about fracturing the tooling ecosystem by having separate, subtly different transpilers
1 reply 0 retweets 2 likes -
@mathias, what we could share is the data itself probably. Re: the transpiler itself, parser, and other dependencies -- there is no need to mix two implementations. We can extract the data (unicode tables, etc) from your implementation into a separate module probably.1 reply 0 retweets 0 likes -
Replying to @DmitrySoshnikov @mathias
I think we could start from https://github.com/mathiasbynens/regenerate-unicode-properties … , which is a JavaScript friendly translation from PropList.txt in UCD tailored for https://github.com/tc39/proposal-regexp-unicode-property-escapes …. We don't have to create another module with subtly different translations.
1 reply 0 retweets 1 like -
However, my major concern is on the package size. The packed size of regenerate-unicode-properties is 85 kB while the one of regexp-tree is only 60.1 kB. The gzipped size of PropList.txt is 25 kB and we could even do better. In this situation we may need get our hands dirty.
3 replies 0 retweets 0 likes -
Replying to @JLHwung @DmitrySoshnikov
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).
1 reply 0 retweets 0 likes -
Replying to @mathias @DmitrySoshnikov
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.
1 reply 0 retweets 1 like
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.
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.