gulp-concat | Streaming concat middleware for gulp | Frontend Framework library

We have not been able to figure this out.

Instead we used the option of runner in GitLab, so that when we merge into develop/master the script runs automatically and:

• builds Vue project
• pushes the content folder to ftp while also renaming it to dist

I solved my problem, it turned out that I accidentally remove my nodemon package from package.json, and I had bad docker compose config. I changed it to this version:

I've figured it out. In my lib.ts I had to change the way I export my class:

I believe that you don't need to import separate parts of the Swiper if you are using the bundled build of Swiper. So, just try the same code without import statements and Swiper.use statement.

Also, don't forget that in the default initialization, it might be helpful to enqueue the Swiper style file to have a default appearance.

If you want to use only the required parts of Swiper, you should include the source file in your source files, not just enqueueing the already built file that is located in the Generatepress.

In copy:css you have this line:

paths.src.base + '/assets/css/argon.css'

where apparently your error is. The problem is your paths.src.base is defined as

base: './' to which you are adding /assets/css/argon.css so you end up with

.//assets/css/argon.css note the two leading backslashes.

Get rid of the leading backslash in the /assets/... and check the rest of your code for the same problem.

Also since you are using gulp4 get rid of runSequence - look at the documentation for gulp.series.

I could see pretty-checkbox's developer last published 4 years ago.

Let's say the new module used popper-js@2.0 and someone who already had popper-js@4.0 as direct or sub-dependency in their project is more likely to face unmet peer dependency on using the new module.

Downgrading the version is not recommended due to possible conflict with other modules. A workaround would be to add resolutions.

Before doing anything, ensure there is no other version of react installed globally, delete your node-modules folder and package-lock.json file. Ensure your package.json dependency has react@15.4.0 and only add popperjs@^1.16.0 if you're sure that other modules in your project are not relying on later versions of popperjs.

Take a look at this article for a good explanation on peer dependencies

If there are other modules that needs other versions of popperjs then in your package.json you could add an additional property at the end like below,

After searching a bit more I found a somewhat feasible solution:
Firstly, you need to do npm i gulp-strip-import-export
Secondly, rewrite the tsWorkload as follows:

Just as I was about to post this question I figured out the problem. Essentially the vue-loader version is incorrect and answering this so another developer doesn't spend hours looking for an answer.

Early on in building the frontend structure for the application I hit an issue where the latest version of Vue in NPM is v2.6.12 and the next version is v3.0.11. Simple enough to resolve just specify the version.

Turns out it's the same issue with vue-loader and at the time of writing the latest version is v15.9.6 whilst the next version is v16.2.0. As you'll note from the included package.json file, the version specified is v15.9.6.

For Vue 3 to work alongside vue-loader it's imperative that the version installed is not below '16.2.0'.

You need to add add/install gulp-watch... i dont see it in your package.json. To add it try: