|
5 | 5 | | master | [](https://github.com/userfrosting/gulp-uf-bundle-assets/actions) [](https://codecov.io/gh/userfrosting/gulp-uf-bundle-assets/branch/master) | |
6 | 6 | | develop | [](https://github.com/userfrosting/gulp-uf-bundle-assets/actions) [](https://codecov.io/gh/userfrosting/gulp-uf-bundle-assets/branch/develop) | |
7 | 7 |
|
8 | | -Orchastrates JS and CSS bundle creation in a highly efficient and configurable manner. |
9 | | - |
10 | | -**CAUTION** The implementation currently produces a great deal backpressure. This can result in signficiant RAM usage. Projects dealing with a significant number resources are better off not using this tool until the custom stream source is implemented in v4. |
| 8 | +Orchastrates JS and CSS bundle creation in an efficient and configurable manner. |
11 | 9 |
|
12 | 10 | ## Install |
13 | 11 |
|
14 | 12 | ```bash |
15 | | -npm install @userfrosting/gulp-bundle-assets --save-dev |
| 13 | +npm i -D @userfrosting/gulp-bundle-assets |
16 | 14 | ``` |
17 | 15 |
|
18 | 16 | ## Usage |
19 | 17 |
|
20 | 18 | ```js |
21 | 19 | // gulpfile.esm.js |
22 | | -import assetBundler from "@userfrosting/gulp-bundle-assets"; |
| 20 | +import AssetBundler from "@userfrosting/gulp-bundle-assets"; |
23 | 21 | import { src, dest } from "gulp"; |
24 | 22 | import cleanCss from "gulp-clean-css"; |
25 | 23 | import concatCss from "gulp-concat-css"; |
@@ -57,7 +55,7 @@ export function bundle() { |
57 | 55 | }; |
58 | 56 |
|
59 | 57 | return src("src/**") |
60 | | - .pipe(assetBundler(config, joiner)) |
| 58 | + .pipe(new AssetBundler(config, joiner)) |
61 | 59 | .pipe(dest("public/assets/")); |
62 | 60 | } |
63 | 61 | ``` |
@@ -85,6 +83,8 @@ It has since been entirely reworked to better suit the requirements of the UserF |
85 | 83 |
|
86 | 84 | This package was previously published under `gulp-uf-bundle-assets` and as of v3 is published under `@userfrosting/gulp-bundle-assets` to assist in longterm project management. |
87 | 85 |
|
| 86 | +As of v4 virtual path logic was extracted into a separate package [@userfrosting/vinyl-fs-vpath](https://github.com/userfrosting/vinyl-fs-vpath). This change enabled a significant simplification of core logic along with a significantly faster and more efficient way to support virtual path mappings. |
| 87 | + |
88 | 88 | ## Release process |
89 | 89 |
|
90 | 90 | Generally speaking, all releases should first traverse through `alpha`, `beta`, and `rc` (release candidate) to catch missed bugs and gather feedback as appropriate. Aside from this however, there are a few steps that **MUST** always be done. |
|
0 commit comments