gulp-cli | Command Line Interface for gulp | Command Line Interface library

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 had the same problem. You should change the import of 'assets/.../variables.scss' to './assets/.../variables.scss'. In my case it was in styles.scss but it can be in every .scss file.

Looking at the package.json you posted in a comment, as of this writing at least, all your issues are in dev dependencies and none are in production dependencies. You can confirm this with npm audit --omit=dev which (as of this writing) shows 0 vulnerabilities.

At this point, a valid option is to decide not to worry about any of those issues reported by npm. You are, for example, extremely unlikely to trigger a denial of service issue via glob-parent (as reported in the snippet you provide) and in the vanishingly-small likelihood that you do, it will be a "denial of service" on your own tooling while running gulp. Literally, who cares?

But if you really want to get rid of these things: uninstall gulp and check-dependencies. The former hasn't published a new version in 2 years and you're not using it in your package.json. The latter hasn't published a new version in 4 years and isn't anything you can't live without. You aren't using either of those dev dependencies in your package.json. If you were planning on using gulp, consider using grunt instead (currently, reports 0 vulnerabilities when installed) or regular npm scripts.

TL;DR:

1. You can choose to ignore these. They are all in dev dependencies, at least as of this writing.
2. If ignoring them is not what you want to do, remove gulp and check-dependencies. You are not using them anyway, at least not yet.

If you are following along with a tutorial, definitely ignore the warnings for the purposes of the tutorial or find a more up-to-date tutorial.

I have FOUND this helpfull for migration to Gulp@4.0.0

https://www.sitepoint.com/how-to-migrate-to-gulp-4/

Kinvey support replied to me, apparently, you have to set your storage type when initializing KinveyModule in the imports of app.module.ts. WebSQL is the current default if it is not set. Kinvey Documentation.

There are two substantial errors in this docker-compose.yml file.

A Docker image only runs one command. In many contexts you can express that in two ways, either as a simple string or as an explicit list of words. The angular image runs a single command:. It has two words, and each word includes embedded spaces and punctuation; it is like running in your shell 'npm install gulp &' 'gulp serve watch', which will produce a similar error.

If a Compose service has both image: and build:, then when you docker-compose build the application, it first builds the image according to build:, then saves it locally under the name image:. What that means in your case is that the image named ubuntu:20.04 is a mash-mash of all three of your applications built together.

What would make this setup actually work? You probably don't need to be actively developing all three of these applications at the same time. Front-end applications also don't really participate in the container ecosystem in many interesting ways; since they ultimately run in the browser and not a container, they can't use Docker networking to reach other containers, for example. You can use docker-compose up to launch this stack, and then use Node on the host to develop, debug, and unit-test an individual part of the application.

The individual images just need to COPY the application code in and RUN npm install:

gulp.task('default', gulp.series('sass', 'watch')) ;

You did never copy or add files to /var/www/html/

May you have choose the wrong destination path in your copy command: COPY src src/

Please consider also that the volume of your docker-compose file is only mounted if your container is running and not while the image is building. A volume can also overlay folder and files, which you did have add in the Dockerfile if the container is running.

You may want to create helper script, which run on start of the container and does chown the folders. https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#entrypoint

In order to serve the static files from a container using the nginx proxy, the nginx proxy must have access to files statically... it would not 'proxy' but 'read' and serve the files... which means you must mount the app files into the proxy...

I would recommend you put up a new, light and clean nginx behind the nginx proxy along with your php-fpm service so you can have full management of your routes/locations,

First of all I have created a docker-compose.yml in my app that contains the following: