gulp-tasks | gulp-tasks-build | Build Tool library

I am trying to compile the scss theme with gulp on Ubuntu 18.04 OS and I get this error:

I am having a similar issue as the question posted here but none of the answers given there apply to my situation.

When I run the one and only task defined in my Gulpfile.js file it is getting executed twice.

I am using Gulp version 4.0.2

This is the contents of my Gulpfile.js file:

Trying to pin down the source of this error when running jest:

Recently I unignored composer.lock along with package-lock.json (likely unrelated), and I changed our gulp deploy script to use composer install instead of composer update. Before pushing new code to prod servers I updated the lock files to the latest using composer update and npm update to make sure there was nothing weird in there from branch merges.

However the gulp deployment script hit various issues, the most problematic of which was: "Requirements could not be resolved to an installable set of packages"

gulp-tasks/deploy.js in its current state:

I've got a gulp task that loops through a folder looking for sub folders and outputs a JavaScript file based upon the contents of each folder. Below is a more visual example.

• src
  • assets
    • scripts
      • critical
        • loadCSS.init.js
      • legacy
        • flexibility.init.js
        • picturefill.init.js
      • modern
        • connectivity.js
        • layzr.init.js
        • menu_list.js
        • scroll-hint.init.js
        • slideout.init.js
        • swiper.init.js
      • service-worker
        • service-worker.js

becomes:

• dev
  • assets
    • scripts
      • critical.js
      • legacy.js
      • modern.js
      • service-worker.js

This is achieved by reading the contents of the src/assets/scripts directory, then running a loop against each folder (critical, legacy, modern, service-worker) and sending the contents of each folder to a Gulp tasks which get merged together with merge-stream.

All this works great, except that once the tasks are merged back together, I want to trigger a notification if the compilation succeeded. If I try to pipe anything to the merged streams, it doesn't work. It just returns the merged streams, and never continues on.

If I un-promisify my PROCESS_SCRIPTS function and don't use merge-stream (i.e. only processing one manually specified folder), it works fine, so I'm at a loss as to what's going on.

Here's my full task:

I've created a script that loops through a bunch of folders and processes them each in to webpack bundles. This works great, except that I can't figure out why the Promise around the loop isn't resolving.

Some things I've tried:

• If I put a console.log("hello world") just before resolve(), within the } else { ... }, it outputs the log.
• If I move resolve() out of the } else { ... }, it resolves, but the rest of my gulp task doesn't continue (separate, but related, issue).

I would appreciate some help in figuring this out. Most relevant chunk of code is below, the rest of it's at the link below.

I currently have a build definition in place to build my project and publish my files for release. My project relies on a bit of NPM to do some automation using Gulp.js. I dont need it for anything else once my gulp-tasks have run.

When I get to my publish artifacts step, it publishes all of the files in the node_modules directory even though I don't even have them in my repo. I was wondering if there was a way to exclude them from within the contents section or if anyone else has a better idea?

Here is my Publish Artifacts settings:

In the Contents section, I also tried:

I have a gulp task that downloads a few JSON files from GitHub, then prompts the user for values to replace in those files. For example, I have an .ftpconfig that gets download, and then the user is asked to enter hostname, username, password, and path.

Because the file first needs to be downloaded before it can be configured, and each file needs to be configured sequentially, I'm using quite a few nested callbacks. I'd like to change this "callback hell" system so that it utilizes async/await and/or promises instead, but I'm having a lot of difficulty understanding exactly why my code isn't working; it seems that promises fire their .then() functions asynchronously, which doesn't make sense to me.

My goals are as follows:

1. Download all config files asynchronously
2. Wait for all config files to finish downloading
3. Read existing settings from the config files
4. Prompt the user for changed settings in each config file synchronously

I've tried a number of approaches, none of which worked. I discarded the code I've used, but here's a rough recreation of the things I've tried:

Attempt #1:

I have used the theme-generator to create a fresh theme. Now I've created a second theme in the same directory and tried to set it's base/parent theme using gulp extend as explained on these pages:

https://github.com/liferay/liferay-theme-tasks https://dev.liferay.com/de/develop/reference/-/knowledge_base/7-0/theme-gulp-tasks

After running the command and choosing option 1) to extend the Base Theme , I get the following options:

1. Styled
2. Unstyled
3. Search globally installed npm modules (development purposes only)
4. Search npm registry (published modules)

No matter if I choose 3) or 4) I cannot find the theme package.

Do I really have to publish the theme to npm to be able to find it?