next.js

a0e02f41 - Thread compile_time_info through webpack path to eliminate hardcoded node_env strings

Thread compile_time_info through webpack path to eliminate hardcoded node_env strings Extract node_env_from_compile_time_info() as a shared helper in parse.rs and use it from both EcmascriptModuleAsset::parse() and the webpack analysis path. Thread compile_time_info through WebpackModuleAsset, WebpackChunkAssetReference, WebpackEntryAssetReference, WebpackRuntimeAssetReference, webpack_runtime(), and module_references() so that SWC plugin transforms on webpack bundles also see the correct NODE_ENV. Add a comment in segment_config.rs explaining why the node_env value is irrelevant there (EcmascriptInputTransforms::empty() = no transforms run). Co-Authored-By: Claude <noreply@anthropic.com>