commit fbf2a9397c823b162341b57eff0bdfb00d2f6f8e
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Fri Jul 7 16:09:23 2023 -0700

dev-node/apinat-converter: relax node dep

commit c9ccf58410ee4c88b29405304068a23905856784
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Fri Aug 26 12:22:51 2022 -0700

dev-node/apinat-converter: finish updates for node 18

commit 6bc94a4122d49af453b75d9b49fa0a4f174ebd4f
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Fri Aug 26 12:20:26 2022 -0700

sync pypy3 compat ebuilds with upstream

commit f462eae536822513d2326aa3849b3c186af52fbe
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed May 25 19:53:19 2022 -0700

dev-node/apinat-converter: add nodejs max ver dep

commit 493d4cf318bb363b974b79ffc62e4b20e6e31c65
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed Feb 2 13:56:04 2022 -0800

dev-node/apinat-converter: force ** keyword

commit e68e2c04cd70133e4bc98c6b46297281d0a2aed7
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Wed Feb 2 13:45:43 2022 -0800

dev-node/apinat-converter: added

updated profile/categories to include dev-node

the approach here is similar to the one we use with maven builds
it is dirty because we run npm install during src_unpack which means
that we are at the mercy of whatever is going on in npm that day,
however, at least this way the process is managed by portage instead of
as a random bash script