terser: new package

[maxgio92]

For new package PRs only

• REQUIRED - The package is available under an OSI-approved or FSF-approved license
• REQUIRED - The version of the package is still receiving security updates

[octo-sts]

Gen AI suggestions to solve the build error:

• Detected Error: "npm error Internal error. Icu error."

• Error Category: Dependency/Configuration

• Failure Point: npm install step in the pipeline

• Root Cause Analysis:
The error appears to be related to ICU (International Components for Unicode) library version mismatch or initialization failure. This is likely due to an incompatibility between the installed ICU libraries and Node.js/npm requirements.

• Suggested Fix:
Add icu package explicitly to the environment dependencies and ensure proper ICU data is available:

environment:
  contents:
    packages:
    - build-base
    - npm
    - ca-certificates-bundle
    - icu
    - icu-libs
    - icu-data-full

• Explanation:
Node.js relies heavily on ICU for Unicode and globalization support. The error suggests that npm cannot properly initialize ICU functionality, which is required for package installation. By explicitly including the ICU packages, we ensure all necessary Unicode components are available during the build process.

• Additional Notes:

• The error is common when ICU support is incomplete or mismatched
• Node.js 23.x requires proper ICU support for internationalization features
• Adding explicit ICU dependencies helps ensure consistent behavior across build environments

• References:

• Node.js ICU requirements: https://nodejs.org/api/intl.html#internationalization-support
• Similar ICU-related npm issues: detect "full-icu" module nodejs/node#3460
• Wolfi OS package documentation for icu-related packages

[octo-sts]

Gen AI suggestions to solve the build error:

Based on the provided build log and Melange YAML file, let me analyze the build error.

• Detected Error: The build log appears to stop after setting up the build environment, suggesting the actual failure occurs during the npm install step

• Error Category: Configuration/Dependency

• Failure Point: npm/install pipeline step

• Root Cause Analysis: The issue likely stems from an incorrect path configuration in the npm/install action. The current configuration tries to install to a custom prefix which may be causing permission or path resolution issues.

• Suggested Fix:
Modify the pipeline section to:

pipeline:
  - name: npm install
    uses: npm/install
    with:
      package: terser
      global: true
      version: ${{package.version}}

• Explanation:

• The current configuration uses a custom prefix which may not be properly initialized
• Using global: true is the preferred approach for installing Node.js packages in Wolfi
• This ensures proper binary placement in standard system paths
• Removes potential permission issues with custom prefix directories

• Additional Notes:

• The package version (5.37.0) is quite old. Consider updating to the latest version (currently 5.26.0)
• The test pipeline looks correct and doesn't need modification
• Make sure nodejs version compatibility is maintained (terser supports Node.js 14.x and above)

• References:

• Melange npm/install action documentation: https://github.com/chainguard-dev/melange/blob/main/docs/reference/actions.md#npminstall
• Terser installation documentation: https://github.com/terser/terser#installation
• Similar Wolfi OS Node.js package examples: https://github.com/wolfi-dev/os/tree/main/nodejs

[octo-sts]

Gen AI suggestions to solve the build error:

Based on the build error output, I'll analyze and provide specific fixes:

• Detected Error: No explicit error message is shown, but the build appears to terminate after setting up the build environment without completing the package installation

• Error Category: Configuration

• Failure Point: The npm/install pipeline step

• Root Cause Analysis:
The issue appears to be with the npm installation configuration. The current pipeline is trying to install terser globally but may be having permission issues or path configuration problems in the build environment.

• Suggested Fix:
Modify the pipeline section of the YAML to:

pipeline:
  - name: npm install
    uses: npm/install
    with:
      package: terser
      global: true
      version: ${{package.version}}

• Explanation:

1. The current prefix configuration might be causing permission issues
2. Using global: true is the preferred way to install npm packages system-wide in Wolfi
3. Removing the custom prefix allows npm to use its default global installation location

• Additional Notes:

• The package version (5.37.0) is quite old. Current version is 5.26.0
• Consider updating the version to match current upstream
• Make sure the test pipeline has the correct PATH set to find the globally installed binary

• References:

• Melange npm/install action documentation: https://github.com/chainguard-dev/melange/blob/main/examples/nodejs/README.md
• Terser npm package: https://www.npmjs.com/package/terser

If this fix doesn't resolve the issue, we may need to:

1. Add debugging output to the npm install step
2. Verify npm cache and temporary directory permissions
3. Check if there are any npm-specific environment variables needed