gulp-run | Pipe to shell commands in gulp | Frontend Framework library

Your DataService service has two constructor parameters, url and http. http can be resolved because it is registered by the HttpClientModule, but the url parameter is not registered in the dependency injection container. That is the reason why you get the error.

I guess you always let inject a specific class, as for example UserDataService, into your components and never a DataService instance.

So you should refactor your DataService to an abstract DataServiceBase class and remove the @Injectable() decorator.

And as yurzui suggested, remove DataService from the list of providers.

The error was fixed by removing the icon definition from config.xml:

First thing I would change is some of your tasks like

gulp.task('scripts',gulp.parallel('templates'), scripts);

gulp.task('build', gulp.parallel('styles', 'scripts','fonts'), build);

gulp.task('run', gulp.parallel('build'), run);

Here is the task signature from the docs (https://gulpjs.com/docs/en/api/task#signature)

task([taskName], taskFunction)

You have gulp.task('run', gulp.parallel('build'), run); that last run has to be part of the argument taskFunction so you probably want :

gulp.task('run', gulp.series('build', run));

gulp.task('build', gulp.series( gulp.parallel('styles', 'scripts','fonts'), build)); and

gulp.task('scripts',gulp.series('templates', scripts));

You may have other issues but start with the above changes.

In these two lines of your code:

Whatever task you want to run you can write in the on change event I think it will work. You can also use event emitter class that will help you to emit the event and on event triggered you can run the task.

React removed createClass from version 16. You can use create-react-class to migrate easily as shown in react documentation.

From my experience, many times such random errors are due to a dirty state one of the test left behind which in turn fails some other test. AFAIK the default order for Karma is not expected or defined. I would try to comment out (binary search style) the first half of the tests and see if it passes consistently.

The answer is no in grunt-usemin, but in one of the dependencies: grunt-filerev. This last module is the one used to create the file revisions of you css, js and other files.

After grunt-filerev is executed (executed as a subtask of grunt-usemin), it creates a summary (stored in within your grunt task, under grunt.filerev.summary). The summary contains the following information:

What I think is happening is, docker run is copying the local node_modules from your project inside the container at COPY . /app .

So thus you get the linux-x64 error. It basically copied all the machine specific code from node_modules to the container that must have another OS. To fix this, ignore node_modules by making a .dockerignore file alongside your package.json and add just one line.

node_modules

Read more about it from here.