You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EZID front-end build pipeline relies on Gulp for tasks including:
SCSS compilation (with sourcemaps and PostCSS processing)
JavaScript linting, bundling, and minification
Image optimization and caching
File inclusion for HTML (e.g., <!--#include file="header.html"-->)
Starting a development server with live reload and SSI (via browsersync)
Running tasks such as cleaning directories, copying assets, and deploying to GitHub Pages
There are some challenges with this approach, specifically:
Gulp dependencies not being actively maintained
The UI and other CDL teams appear to have switched to other/more modern tooling alternatives
Desired State/Solution
Investigate migrating the build pipeline from Gulp to a more modern system, such as NPM scripts or a similar service, identify any package gaps or where custom build scripts would be necessary.
Tasks
Audit current Gulp tasks to identify all tasks/dependencies that would need replacement
Incrementally test replacement of each Gulp task with an equivalent NPM-based or similar script
Test full build process, verifying CSS and JS outputs
The text was updated successfully, but these errors were encountered:
I'm a tiny bit familiar with Webpack since Webpacker became popular in common Rails setups (Webpacker is a Ruby wrapper around the javascript Webpack library). I don't know much about Vite, but just that it's another popular alternative for compiling assets down into a more minified form that doesn't change too often and can be loaded once and reused from cache for subsequent page loads.
I believe these may be the most used NPM libraries for these particular kinds of tasks right now, though I'm not extremely up-to-date about these aspects. We can also check in with Joel H. to see if he has a way of working that he and other services are used to.
Current State/Issue
The EZID front-end build pipeline relies on Gulp for tasks including:
<!--#include file="header.html"-->
)There are some challenges with this approach, specifically:
Desired State/Solution
Investigate migrating the build pipeline from Gulp to a more modern system, such as NPM scripts or a similar service, identify any package gaps or where custom build scripts would be necessary.
Tasks
The text was updated successfully, but these errors were encountered: