Hi, I've found that the upstream author for @unicode packages uses node-unicode-data to generate the unicode data for all @unicode packages.
I was thinking that we could replace all current and future @unicode packages with node-unicode-data instead of having separate packages for them. The workflow I am proposing is that we pass the unicode version as a parameter to node-unicode-data and it will download and generate the unicode data for that version. node-unicode-data is not a published npm package so here is the git repo: https://github.com/node-unicode/node-unicode-data. @unicode packages are only used as build dependencies. I'd be happy to work on the package if the suggestion is agreed upon. Regards.
-- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
