On Thu, 2020-11-05 at 07:17 +0200, Andrius Merkys wrote: > I was aware of node-fn-name at the time I uploaded node-fn.name. > However, due to my lack of experience with NodeJS I did not compare the > packages to understand the difference of their APIs and functionality. I > would love to deduplicate (maybe by removing node-fn.name which should > have less reverse dependencies), but I need someone to confirm that > these packages could be used interchangeably, or provide patching > suggestions if APIs are different.
Based solely on the usage information in the README, their APIs are compatible, so just changing from fn.name to fn-name or vice versa in the require() call will be enough to switch between them. I'm not sure which one is better, but fn-name started earlier and has more recent commits than fn.name. The fn-name README inspires more confidence in me since the example uses const instead of var to store the name finding function. I don't know much about JavaScript nor NodeJS, but my intuition says const seems to be more correct for importing functions. StackOverflow agrees: https://stackoverflow.com/questions/55948935/const-vs-var-in-nodejs-require-statement I noticed that neither fn-name nor fn-name have any reverse dependencies in Debian so perhaps they should just both be removed? I also noticed that fn-name is outdated in Debian compared to upstream. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
