Bug 2457184
| Summary: | nodejs-esbuild: fails to install from EPEL 9 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Carl George 🤠<carlwgeorge> |
| Component: | golang-github-evanw-esbuild | Assignee: | W. Michael Petullo <redhat> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel9 | CC: | go-sig, mike, redhat |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | golang-github-evanw-esbuild-0.27.2-2.el9 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-06-19 00:48:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Carl George ðŸ¤
2026-04-09 23:42:16 UTC
I looked into this a bit, and the dependency seems to be generated from this part of the source code. https://github.com/evanw/esbuild/blob/v0.27.2/npm/esbuild/package.json#L15 EPEL packages can only require default packages, not alternate module streams. RHEL 9 defaults to nodejs 16. The last version of esbuild that worked with nodejs 16 was 0.21.5. https://github.com/evanw/esbuild/blob/v0.21.5/npm/esbuild/package.json#L15 As far as I can tell, there are two options here. * Downgrade golang-github-evanw-esbuild to version 0.21.5 for compatibility with nodejs 16. * Remove the nodejs-esbuild subpackage from the epel9 spec file (either by deleting it or wrapping it in a disabled conditional). Which one sounds better to you Mike? Carl, have to investigated which EPEL packages depend on golang-github-evanw-esbuild? I originally created an epel9 branch of the golang-github-evanw-esbuild package in response to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2457184. I don't know if they ever followed up to create the Chromium package the bug mentions. I usually deal with EPEL only when prompted. I am not a nodejs user, so I cannot judge the implication of removing the nodejs-esbuild subpackage. My instinct is that should be the way forward. I would think that downgrading a package would be frowned upon. You linked to this bug (the one we're commenting in) but I think you meant to link to bug 2361107 where the chromium maintainer requested an EPEL 9 build. Chromium was added to EPEL 9 and is regularly updated. The only package I can find that depends on golang-github-evanw-esbuild is chromium, as a build requirement. If you did want to go the downgrade route in order to keep nodejs-esbuild, then you could try to downgrade it in a copr repo and then rebuild chromium in the same copr. You're right that downgrading should generally be avoided, but in this case I would say it's justified for the nodejs compatibility. Nothing requires or build requires nodejs-esbuild, so in theory it should be safe to remove. At the very least it can't hurt anything, because functionally an uninstallable package is no different than a non-existent one. I agree with your instinct that this is a better way forward. Here's a pull request to implement that with a conditional. https://src.fedoraproject.org/rpms/golang-github-evanw-esbuild/pull-request/18 FEDORA-EPEL-2026-5d3e152c80 (golang-github-evanw-esbuild-0.27.2-2.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-5d3e152c80 FEDORA-EPEL-2026-5d3e152c80 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-5d3e152c80 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2026-5d3e152c80 (golang-github-evanw-esbuild-0.27.2-2.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |