edp-build

library1.2.4jsnpmunverified

edp-build is a package that serves as the build component for the ecomfe Enterprise Develop Platform (EDP), an older Node.js and npm-based command-line interface for enterprise frontend development. It was designed to handle various build-related tasks such as processing and optimizing frontend assets, including JavaScript (especially AMD modules), CSS, and images, often in conjunction with plugins like `edp-build-inline` and `edp-build-fontmin`. The package is currently at version 1.2.4. However, the entire EDP ecosystem, including edp-build, appears to be abandoned, with the main `edp` CLI last updated in 2017 and `edp-build` itself in 2016. Consequently, there is no active release cadence, and it is largely incompatible with modern frontend development practices or recent Node.js versions. Its original key differentiation was its integrated suite of tools for a specific enterprise frontend ecosystem in China, focusing on older module paradigms.

devops web-framework

npm install edp-build

github ↗package ↗

INSTALL

IMPORT

SIG · EDP-BUILD

edp-build

devopsjavascriptv1.2.4

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

EDP Build Commands

✓ edp build <command>

✗ import { build } from 'edp-build'

edp-build is primarily a CLI tool and a component of the `edp` command-line interface. It is not designed for direct programmatic import as a JavaScript module in user code. Functionality is exposed via `edp` global commands.

Global CLI Installation

✓ npm install -g edp edp-build

✗ npm install edp-build

The `edp` platform and its components, including `edp-build`, are typically installed globally to be accessible as command-line tools. Local installation without `edp` globally is not how it's intended to be used.

Demonstrates global installation of `edp` and `edp-build`, and basic command-line usage for build-related tasks.

npm install -g edp edp-build # Navigate to your project root cd my-old-edp-project # Example: List AMD modules in biz.js (from original README) # This checks for potential issues if a module is listed multiple times. edp amd list biz.js | sort | uniq -c | sort -k 1 -n -r | awk '{if($1>1){print $0}}' # Example: Run a generic build process (requires edp-build configuration in project) # This assumes a project configured with edp build pipelines. edp build # Example: Specific build command for release edp release --config=release-config.js

edp --version

Debug

Known issues

breakingThe entire `ecomfe/edp` platform, including `edp-build`, is considered abandoned. The last significant update to `edp` was in 2017, and `edp-build` in 2016. It is highly unlikely to be compatible with modern Node.js versions or current frontend development tools and practices.

fix

Do not use for new projects. For existing projects, consider migrating to a modern build system (e.g., Webpack, Rollup, Vite, Gulp) or maintaining a specific legacy Node.js environment if migration is not feasible.

affects: >=1.0.0

gotcha`edp-build` relies heavily on older frontend module systems like AMD. Its processors and configurations are tailored for these paradigms and may not work with ES Modules (ESM), CommonJS (CJS) in modern contexts, or contemporary bundler configurations.

fix

Ensure your project strictly adheres to the AMD module format and older project structures expected by EDP. Avoid mixing with modern JavaScript features or module systems.

affects: >=1.0.0

gotchaDue to its abandonment, `edp-build` and its underlying dependencies may contain unpatched security vulnerabilities. Using it in production environments without thorough security auditing is not recommended.

fix

Perform a comprehensive security audit of all `edp` ecosystem dependencies or, preferably, migrate to actively maintained tools. Isolate legacy systems in secure, controlled environments if use is unavoidable.

affects: >=1.0.0

breakingCompatibility issues with newer Node.js versions are highly probable. Users often encounter `node-gyp` errors during installation or runtime errors due to breaking API changes in Node.js.

fix

Pin your project to an older, compatible Node.js version (e.g., Node.js 6 or 8) using tools like `nvm` or Docker. This is often essential for installation and execution.

affects: >=1.0.0

Errors

Common errors & fixes

Error: `node-gyp` failed with exit code: 1

Native dependencies failing to compile against newer Node.js versions.

fix

Install a legacy Node.js version (e.g., Node.js 6 or 8) using `nvm` (`nvm install 8 && nvm use 8`) or ensure you have necessary build tools (Python 2.7, Visual C++ Build Tools on Windows) installed.

'edp' is not recognized as an internal or external command, operable program or batch file.

The `edp` CLI tool, which orchestrates `edp-build`, is not installed globally or not in the system's PATH.

fix

Ensure `edp` and `edp-build` are installed globally: `npm install -g edp edp-build`. Verify your system's PATH includes npm's global bin directory.

Upgrade

Version history

1.2.4latest on npm

Audit

Dependencies

edp-corerequiredCore utilities for the EDP platform.

edprequiredThis package is a component of the 'edp' command-line tool, not a standalone library.

Agent activity

2 hits · last 30 days

node

Resources

githubhttps://github.com/ecomfe/edp-build ↗

packagehttps://www.npmjs.com/package/edp-build ↗