vercel/ncc

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

Open

#1247 opened on Jan 27, 2025

View on GitHub
 (6 comments) (1 reaction) (0 assignees)JavaScript (8,841 stars) (273 forks)batch import
help wanted

Description

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

Contributor guide

Tech stack
javascriptnodejs
Domain
build systemtoolingci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsJavaScriptncc basicswebpack targets
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.