gulp-sass | SASS plugin for gulp | Style Language 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 fixed the problem by adding npm i --save-dev sass.

In your watchTask you have this:

src/**/*.+(scss|sass) note the + sign before the alternation.

But in your styleLink variable you have:

Try defining your "sprite" task before it gets called in the "local-development" task (and any others that may fall into the same pattern).

When creating tasks via the gulp.task(...) form you do need to have those tasks created (so they can be registered) prior to their being called. Otherwise you will forward-referencing them.

Forward references

A forward reference is when you compose tasks, using string references, that haven't been registered yet. This was a common practice in older versions, but this feature was removed to achieve faster task runtime and promote the use of named functions.

In newer versions, you'll get an error, with the message "Task never defined", if you try to use forward references.

• from Forward reference documentation

One advantage of the function myGulpTask() {...} form of creating tasks is that do not need to be declared prior to calling them.

gulp-sass 4.1.0 uses node-sass 4, and node-sass 4 does not support Node.js 16, as indicated in this table.

To support Node.js 16, upgrade gulp-sass: the latest version today is 5.1.0:

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.

gulp is not placing its output files relative to your working directory. It will place output files as configured in your gulpfile. When the build starts, gulp is changing the working directory back to the project root:

[19:19:04] Working directory changed to /builds/stefan_avramovic/nodejs-code-build
[19:19:04] Using gulpfile /builds/stefan_avramovic/nodejs-code-build/gulpfile.js

Thus, as according to your target configurations, your outputs will be placed in the dist and public directories, relative to the project root, not my-build -- the dest paths are going to be defined the same way gulp is finding your src files using the defined relative paths.

To fix this you could:

1. change the directory you artifact to your dist/public directories, as gulp is currently using
2. change your gulp config -- use a different target of my-build or set cwd accordingly in your gulp dest options
3. move the target directories after the build is finished (e.g. mv $CI_PROJECT_DIR/dist $CI_PROJECT_DIR/my-build)

I would import from 'sass' with a different name, and construct sass per function call, just like when using require.