vercel/ncc

would you be open to support node[[X].Y] as target to make GitHub Action build artifacts smaller?

Open

#1,247 建立於 2025年1月27日

在 GitHub 查看
 (6 留言) (1 反應) (0 負責人)JavaScript (8,841 star) (273 fork)batch import
help wanted

描述

in the light of 1246 I discovered default target is es2025 and it only es* targets are expected. underlying webpack does support node* as a target, but ncc restricts it. but using es version as a target doesn't make sense for nodejs versions, because es support is fragmented.

I'd like to relax es* only target restriction to include node* as well, to make GitHub Action build artifacts smaller by not transpiling everything to es2015 but rather only to what's missing in node20 for example

貢獻者指南

技術棧
javascriptnodejs
領域
build systemtoolingci cd
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Node.jsJavaScriptncc basicswebpack targets
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Start by examining the source code of ncc to locate where target validation occurs (likely in the webpack configuration). Look at issue #1246 for context on why targets matter. Check the existing allowed targets list and consider extending it to include node versions. Review any webpack documentation on node targets. The PR should update the validation to accept node versions and possibly adjust the default target based on environment.