There are many packages requiring nodejs as a build time dependency, chromium among others, which requires inspector. Unless there's some complication, enabling inspector shouldn't take noticeably longer to compile. Please enable it for the binary package on the binhost if possible.
In a discussion on IRC it was suggested this could as well be a bug against the package to enable inspector by default in the ebuild. However I hesitated to edit it as it doesn't feel right to me to have e default use flag changed for all users because of the binary package. I'm not sure what the consequences will be and I'm just mentioning it here for the developers/maintainers to take in account and decide what could be the best course of change, if at all.
CC williamh as the nodejs maintainer. I think enabling the USE flag by default reasonable - I've certainly had to recompile nodejs entirely when I needed to quickly debug something. We can certainly do a variant binpkg to make it easier, and I'm happy to run some numbers when I'm done with Chromium today to confirm that it's not adding another 30% to the compile or something.
I will default-enable inspector on new releases of nodejs from this point as I add them to the tree.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=898d9afb6b114031d76ca52a6947662a019bbff5 commit 898d9afb6b114031d76ca52a6947662a019bbff5 Author: William Hubbs <williamh@gentoo.org> AuthorDate: 2025-03-25 22:56:03 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2025-03-25 22:56:22 +0000 net-libs/nodejs: add 20.19.0 Bug: https://bugs.gentoo.org/949653 Signed-off-by: William Hubbs <williamh@gentoo.org> net-libs/nodejs/Manifest | 1 + net-libs/nodejs/nodejs-20.19.0.ebuild | 274 ++++++++++++++++++++++++++++++++++ 2 files changed, 275 insertions(+)
