Gathering detailed insights and metrics for ng-extra-build
Gathering detailed insights and metrics for ng-extra-build
Gathering detailed insights and metrics for ng-extra-build
Gathering detailed insights and metrics for ng-extra-build
npm install ng-extra-build
Typescript
Module System
Node Version
NPM Version
JavaScript (99.8%)
CSS (0.2%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
1 Stars
20 Commits
9 Branches
1 Contributors
Updated on Jul 26, 2019
Latest Version
1.4.0
Package Id
ng-extra-build@1.4.0
Unpacked Size
22.34 kB
Size
5.87 kB
File Count
15
NPM Version
6.9.0
Node Version
10.16.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
ng-extra-build
is a build tool for angular-cli
, you can use this for extra building tasks that angular-cli
can't do, especially for multi-environment.
css
file for the specified environment.i18n
files for the specified environment.npm install ng-extra-build --save-dev
After ng-extra-build
installation is completed, you can find a configuration file named build.conf.json
in $your_project_dir
, you should modify this file as your requirements. See Configuration Reference.
Append below command after angular-cli
build command:
ng-extra-build -env=envName -config=config-file-path
For example, if neware
is one of your envoriment name, add below json content in $Your_project_dir/package.json
:
1{ 2 ... 3 "scripts": { 4 "ng": "ng", 5 "start": "ng serve", 6 "neware": "ng build -prod -sm=false -aot -e neware && ng-extra-build -env=neware" 7 }, 8 ... 9}
And then execute command
npm run neware
to build application for production.
Argument | Required | Default | Description |
---|---|---|---|
-env | true | null | Envrionment name |
-config | false | build.conf.json | Configuration file path. The file path is relative to current working direction (same as path.cwd() in nodejs ) |
base (object
): The base config.
string
): The output directory for build results.This value must set be same as outDir
in Angular CLI.copy (array
): Copy resources into outDir
.
string
): Source file which will be copied.string
): Destination file which will be copied to.css (object
): Css compile options.
string
): Source css file.string
): Destination css file.string
): The css href
in tag <link>
in index.html
for the development environment.After build, will replace this href
with production environment href
.i18n (object
): Build options for i18n files
string
): Directory of source i18n filesstring
): Directory of extra i18n filesstring
): Directory of target i18n filesreplacement (array
): Replacement configurations
string
): The file (path) you want to execute the replacement.array
): Contents you want to replace.
string
): Contents you want to replace.string
): Contents you want to replace withobject
): Contents you want to replace with for the specified environment. key is environment name, value is corresponding content you want to replace with.deletion (array
): Files you want to delete.
compression (object
): Compression configurations.
1{ 2 "$schema": "./node_modules/ng-extra-build/schema.json", 3 "base": { 4 "outDir": "dist" 5 }, 6 "copy": [ 7 { 8 "from": "$root/src/env/$env/favicon.ico", 9 "to": "$dist/favicon.ico" 10 } 11 ], 12 "css": { 13 "from": "$root/src/env/$env/css/theme.css", 14 "to": "$dist/assets/css", 15 "devUrl": "env/neware/css/theme.css" 16 }, 17 "i18n": { 18 "source": "$root/src/assets/i18n", 19 "extra": "$root/src/env/$env/i18n", 20 "target": "$dist/assets/i18n" 21 }, 22 "replacement": [ 23 { 24 "file": "$dist/index.html", 25 "contents": [ 26 { 27 "replace": "Neware Club", 28 "withEnv": { 29 "neware": "Neware RSP", 30 "joy": "Joytele RSP" 31 } 32 } 33 ] 34 } 35 ], 36 "deletion": [ 37 "$dist/env" 38 ], 39 "compression": { 40 "from": "$dist", 41 "to": "$root" 42 } 43} 44
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/20 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
27 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More