arnaud73/ngx-matomo

Matomo (aka. Piwik) web analytics for Angular applications

ngx-matomo's Issues

v0.1.4 : make a new tag to allow SSR fix

Hi,
I am using your library at v0.1.4, the latest tag at time of writing.
It is possible to release a new tag so the SSR fix would be available ?
Thanks :)

Update to Angular 7

Can you please update the project to Angular Version 7?
I've tried with a pull request but am obviously getting some errors in the build pipeline that I am unable to resolve...
An update would be greatly appreciated!
Cheers, Mike

Error TS2694 when building app on Angular 11

After getting the 0.1.4 version to work in my app, I tried upgrading to 1.0.0-rc.1 and the build failed. Found it weird that 0.1.4 worked and this didn't so I figured it's time to ask for help. Any thoughts on the error below? Pasted my env too. I've tried:

1. Cleaning/reinstalling node_modules
2. Removing references to injector from my code

Found some other GitHub threads that have a similar error
angular/angular#35291 (comment)
sclausen/ngx-mqtt#137

Error: node_modules/ngx-matomo/lib/matomo-injector.service.d.ts:19:21 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

19     static ɵfac: i0.ɵɵFactoryDeclaration<MatomoInjector, never>;
                       ~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo-injector.service.d.ts:20:22 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.

20     static ɵprov: i0.ɵɵInjectableDeclaration<MatomoInjector>;
                        ~~~~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo-route-tracker.service.d.ts:48:21 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

48     static ɵfac: i0.ɵɵFactoryDeclaration<MatomoRouteTracker, never>;
                       ~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo-route-tracker.service.d.ts:49:22 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.

49     static ɵprov: i0.ɵɵInjectableDeclaration<MatomoRouteTracker>;
                        ~~~~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo-tracker.service.d.ts:709:21 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

709     static ɵfac: i0.ɵɵFactoryDeclaration<MatomoTracker, never>;
                        ~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo-tracker.service.d.ts:710:22 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.

710     static ɵprov: i0.ɵɵInjectableDeclaration<MatomoTracker>;
                         ~~~~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo.module.d.ts:27:21 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 
'ɵɵFactoryDeclaration'.

27     static ɵfac: i0.ɵɵFactoryDeclaration<MatomoModule, never>;
                       ~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo.module.d.ts:28:21 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 
'ɵɵNgModuleDeclaration'.

28     static ɵmod: i0.ɵɵNgModuleDeclaration<MatomoModule, never, never, never>;
                       ~~~~~~~~~~~~~~~~~~~~~


Error: node_modules/ngx-matomo/lib/matomo.module.d.ts:29:21 - error TS2694: Namespace '"[AppPath]/src/angular-app/node_modules/@angular/core/core"' has no exported member 
'ɵɵInjectorDeclaration'.

29     static ɵinj: i0.ɵɵInjectorDeclaration<MatomoModule>;
                       ~~~~~~~~~~~~~~~~~~~~~


Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 131:10-28
"export 'ɵɵFactoryTarget' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2054:10-28
"export 'ɵɵFactoryTarget' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2231:10-28
"export 'ɵɵFactoryTarget' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2335:10-28[0m
"export 'ɵɵFactoryTarget' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 139:0-27
"export 'ɵɵngDeclareClassMetadata' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2062:0-27
"export 'ɵɵngDeclareClassMetadata' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2239:0-27
"export 'ɵɵngDeclareClassMetadata' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2351:0-27
"export 'ɵɵngDeclareClassMetadata' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 123:22-43
"export 'ɵɵngDeclareFactory' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2046:21-42
"export 'ɵɵngDeclareFactory' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2217:26-47
"export 'ɵɵngDeclareFactory' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2321:20-41
"export 'ɵɵngDeclareFactory' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 133:23-479m
"export 'ɵɵngDeclareInjectable' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2056:22-46
"export 'ɵɵngDeclareInjectable' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2233:27-51
"export 'ɵɵngDeclareInjectable' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2343:20-42
"export 'ɵɵngDeclareInjector' (imported as 'i0') was not found in '@angular/core'

Error: ./node_modules/ngx-matomo/fesm2015/ngx-matomo.js 2337:20-42
"export 'ɵɵngDeclareNgModule' (imported as 'i0') was not found in '@angular/core'

Environment

ng v

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 11.1.4
Node: 12.18.3
OS: win32 x64

Angular: 11.1.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes
Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1101.4
@angular-devkit/build-angular   0.1101.4
@angular-devkit/core            11.1.4
@angular-devkit/schematics      11.1.4
@angular/cli                    11.1.4
@schematics/angular             11.1.4
@schematics/update              0.1101.4
rxjs                            6.6.3
typescript                      4.1.5

Thanks!

Could it using an old version of the code?

Hi I review the code and it's adding piwik.js like this

g.src = !!scriptUrl ? scriptUrl : u + 'piwik.js';

but the new code is adding matomo.js

g.src=u+'matomo.js';
Is it working right?

UserId

There is this line this.matomoTracker.setUserId('UserId');, is the string UserId supposed to be replaced by your own userId ? What are the recommendation for that, and hash stored on localStorage ?

Possibility to add tracking for form analytics

Would it be possible to add a function to do form analytics with matomo. I have read the guide and I don't think it would be too hard to implement.
https://developer.matomo.org/guides/spa-tracking

It should include this function:
_paq.push(['FormAnalytics::scanForForms', documentOrElement]);

Support of Angular 9

Angular 9 has some very nice new features such as the new Ivy compiler reducing app-size and also support for newer versions of TypeScript.

It would be awesome if ngx-matomo would support the new version.

Doesn't work for Angular 10

Even though the readme says that this works with Angular 5, 6, 7 and 8, I managed to install it on an angular 9 app with no problems. Now that Angular 10 is out there, is there any plan to make it compatible with Angular 10?

trackPageView

Hi,
something is not clear for me. Is it necessary to call matomoTracker.trackPageView() to track a page view ? It seems it is to see it in the matomo dashboard.
Example of code (Angular 8), with a singleton service injected in components, and a call of trackPageViewToMatomo from the ngOnInit() of these components:

`
constructor(private matomoTracker: MatomoTracker, private userService: UserService) { }

trackPageViewToMatomo(router: Router, route: ActivatedRoute) {

const pageUrl = router.url;
const pageComponent = route.component['name'];
// this.matomoTracker.enableHeartBeatTimer(10);
// this.matomoTracker.enableLinkTracking(true);
this.matomoTracker.setUserId(this.userService.getUserLogin());
this.matomoTracker.setCustomUrl(pageUrl);
this.matomoTracker.setDocumentTitle(pageComponent);
// this.matomoTracker.setGenerationTimeMs(0); // if compute of page generation time
this.matomoTracker.trackPageView();
}
`

The issue i have is the call of trackPageView leads to browser freezes (chrome and firefox), even if i do this call in a delayed observable.

With routeTracking enabled, matomo's request says in pending sometimes.

The code in the demo seem to be not correct

In app.component.ts you have:

constructor(private matomoInjector: MatomoInjector, 
private matomoTracker: MatomoTracker) {
    this.matomoInjector.init(
      'http://ngx.matomo.cloud/',
      1,
      '//cdn.matomo.cloud/ngx.matomo.cloud/matomo.js'
    );
  }

Which will result in the following error:

Expected 2 arguments, but got 3.

Is this the correct usage?

constructor(private matomoInjector: MatomoInjector, 
private matomoTracker: MatomoTracker) {
    this.matomoInjector.init(
      'http://ngx.matomo.cloud/',
      1
    );
  }

Pass Custom Dimension data with each request

Add the ability to send Custom Dimension data with each request as opposed to having to set and delete globally per page with setCustomDimension and deleteCustomDimension before and after each request.

Support for multiple tracker instances / addTracker

Greetings,

The library doesn't seem to support the addTracker command and a way to handle multiple trackers from different servers.

See https://developer.matomo.org/guides/tracking-javascript-guide#multiple-piwik-trackers

Is there a way to handle this and create multiple tracker instances with the current implementation?

Cheers

Initialize Matomo via Root Component

I have a single page application built in Angular5, I'm using ngx-matomo vs 0.1.4.
this.matomoInjector.init('YOUR_MATOMO_URL', YOUR_SITE_ID); gives me 404.
How can I solve the problem? It's my matomo_url or site_id incorrect?
Shall I stick to ngx-matomo vs 0.1.4. or shall I move to another version? thanks

Not updated on npmjs?

Hi @Arnaud73, I just tried to install the package and it resolves to a 0.2.0 version by eduardmarcinco.
Maybe it's my local acting up but could you perhaps double check it's updated on npmjs properly?
https://www.npmjs.com/package/ngx-matomo

EDIT: nvm doing npm install --save [email protected] fixes my problem.. not aware it was still an rc

Angular 13 compatibility

in Angular 13, NgModuleFactoryLoader was removed

See here : https://update.angular.io/?l=3&v=12.0-13.0
last point : The route package no longer exports SpyNgModuleFactoryLoader and DeprecatedLoadChildren. In case you use them, make sure you remove their corresponding import statements.

error on build :
Error: node_modules/ngx-matomo/node_modules/@angular/router/router.d.ts:21:10 - error TS2305: Module '"@angular/core"' has no exported member 'NgModuleFactoryLoader'.

How to disable link tracking?

In matomo-configuration.ts the default setting for trackLinks is true. Is there any way to completely disable link tracking?
I have tried to use the enableLinkTracking(false) method on the tracker, but that does not stop links from being tracked, it only seems to stop middle- and right-button mouseclicks on URLs from being tracked.

I am only interested in event logging of clicks and navigation actions within my application (which work perfectly fine with ngx-matomo).

How can I completely disable the logging of clicks on URLs that result in requests like this?
my.domain.com/application/matomo.php?link=https://my.target.url

Remove Query Params from url paths

Support Angular 15

Update project dependencies to angular 13, if this is not possible we will no longer use your package

Update project dependencies to angular 13, if this is not possible we will no longer use your package

How to init matomo _after_ user has accepted terms?

We've an issue because we don't want to initialize Matomo, before user has accepted the terms of service. How would we do this?

For now it looks like that init is causing that matomo is loaded before user has accepted this.

Property 'forRoot' does not exist on type 'typeof MatomoModule'

I faced the issue when I installed the ngx-module and tried to import this one.

No provider for Router! Angular 12 Matomo 1.0.0-rc.1

Hi,

I have issue with routeTracking functionality in Angular 12, when I enable it to true like in README file all I get is missing Router provider error.

My deps are:

"dependencies": { "@angular-devkit/schematics": "12.0.2", "@angular/animations": "^12.0.0", "@angular/cdk": "^12.0.2", "@angular/common": "^12.0.0", "@angular/compiler": "^12.0.0", "@angular/core": "^12.0.0", "@angular/forms": "^12.0.0", "@angular/material": "^12.0.2", "@angular/platform-browser": "^12.0.0", "@angular/platform-browser-dynamic": "^12.0.0", "@angular/router": "^12.0.0", "@angular/upgrade": "^12.0.0", ... "ngx-matomo": "^1.0.0-rc.1", ... }

When routeTracking is set to false everything looks fine. I've also tried to set it to false and run MatomoRouteTracker startTracking method manually at later point but it's the same issue.

It occurs for lazy loading routes.

Error During Testing

I'm running ngx-matomo 0.1.2 using Angular CLI: 7.3.6, Node: 10.13.0, and Angular: 7.2.9. It works great but on only one of my tests (using "ng test"). Every other component test passes just fine. This one test only always fails with this error:
TypeError: Cannot read property 'push' of undefined at MatomoTracker.push../node_modules/ngx-matomo/ngx-matomo.es5.js.MatomoTracker.setDocumentTitle (http://localhost:9876/_karma_webpack_/webpack:/node_modules/ngx-matomo/ngx-matomo.es5.js:701:1) at new ApiDetailComponent (http://localhost:9876/_karma_webpack_/webpack:/src/app/api-detail/api-detail.component.ts:30:24) at createClass (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:22159:1) at createDirectiveInstance (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:22028:1) at createViewNodes (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:23254:1) at createRootView (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:23168:1) at callWithDebugContext (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:24176:1) at Object.debugCreateRootView [as createRootView] (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:23686:1) at ComponentFactory_.push../node_modules/@angular/core/fesm5/core.js.ComponentFactory_.create (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/core.js:21507:1) at initComponent (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/fesm5/testing.js:1916:1)

The app builds ok andruns fine. It's just the test that fails. My test is very simple"
it('should create', () => { expect(component).toBeTruthy(); });

Any ideas?

Remove ID's from url paths

Dynamic configuration of scriptUrl, trackerUrl and siteId

I am using the latest version of ngx-matomo (1.1.0). As per the documentation, I have the following set up:

app.module.ts

imports: [
MatomoModule.forRoot({
      scriptUrl: '',
      trackers: [
        {
          trackerUrl: '',
          siteId: 0
        }
      ],
      routeTracking: {
        enable: true
      }
    })
]

app.component.ts

import { MatomoTracker } from 'ngx-matomo';
import { AppConfigService } from './services/app-config.service';

 constructor(
private readonly matomoTracker: MatomoTracker,
private readonly appConfigService: AppConfigService
) {
    this.matomoTracker.setApiUrl(this.appConfigService.matomoUrl().concat('matomo.js'));
    this.matomoTracker.setTrackerUrl(this.appConfigService.matomoUrl());
    this.matomoTracker.setSiteId(this.appConfigService.matomoSiteId());
}

I am using an application config service to pull configurations mentioned in appConfig.json and dynamically set the Matomo Configuration, as per environment. Is there a recommended approach to set the scriptUrl, trackerUrl and siteId dynamically?

Page views & events only visible in user profile, not registered as "Behaviour"

Running Angular 12 & ngx-matomo (1.0.0-rc.1) I’ve setup some test events and page views which are registering in the Matomo dashboard and clearly visible when I click “view user profile”. However, these navigations and events are not showing up in the “behaviour” tab under “pages” or “events”.

This is the module setup:

    MatomoModule.forRoot({
      scriptUrl: `${matomoUrl}/matomo.js`,
      trackers: [
        {
          trackerUrl: `${matomoUrl}/matomo.php`,
          siteId: 3
        }
      ],
      routeTracking: { enable: true }
    }),

and on every NavigationEnd I’m logging a page view, which is being executed on every navigation:

  trackPageView(page: string) {
    this.matomoTracker.setCustomUrl(page);
    this.matomoTracker.setDocumentTitle(page);
    this.matomoTracker.trackPageView();
  }

this is used for event tracking:
this.matomoTracker.trackEvent(category, action, name, value);

Why are these page views and events only showing up on the dashboard, but not under behaviour?
What is still missing?

This could have something to do with URL segmentation?

Yes, I’m looking at the right day & website, stuff is showing up, just not where it should be.
Thanks very much

A/B testing plug-in functions

Hello,

I'm trying to use the Matomo A/B testing plug-in for Angular.
Will you be adding the plug-in functions too in the next release?
Thanks.

Error TS2694 when building app on Angular 9

ERROR in node_modules/ngx-image-cropper/lib/services/crop.service.d.ts:13:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

13     static ɵfac: i0.ɵɵFactoryDeclaration<CropService, never>;
                       ~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/services/crop.service.d.ts:14:22 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.

14     static ɵprov: i0.ɵɵInjectableDeclaration<CropService>;
                        ~~~~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/services/cropper-position.service.d.ts:12:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

12     static ɵfac: i0.ɵɵFactoryDeclaration<CropperPositionService, never>;
                       ~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/services/cropper-position.service.d.ts:13:22 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.

13     static ɵprov: i0.ɵɵInjectableDeclaration<CropperPositionService>;
                        ~~~~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/services/load-image.service.d.ts:15:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

15     static ɵfac: i0.ɵɵFactoryDeclaration<LoadImageService, never>;
                       ~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/services/load-image.service.d.ts:16:22 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.

16     static ɵprov: i0.ɵɵInjectableDeclaration<LoadImageService>;
                        ~~~~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/component/image-cropper.component.d.ts:101:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

101     static ɵfac: i0.ɵɵFactoryDeclaration<ImageCropperComponent, never>;
                        ~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/component/image-cropper.component.d.ts:102:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵComponentDeclaration'.

102     static ɵcmp: i0.ɵɵComponentDeclaration<ImageCropperComponent, "image-cropper", never, { "imageChangedEvent": "imageChangedEvent"; "imageURL": "imageURL"; "imageBase64": "imageBase64"; "imageFile": "imageFile"; "format": "format"; "transform": "transform"; "maintainAspectRatio": "maintainAspectRatio"; "aspectRatio": "aspectRatio"; "resizeToWidth": "resizeToWidth"; "resizeToHeight": "resizeToHeight"; "cropperMinWidth": "cropperMinWidth"; "cropperMinHeight": "cropperMinHeight"; "cropperMaxHeight": "cropperMaxHeight"; "cropperMaxWidth": "cropperMaxWidth"; "cropperStaticWidth": "cropperStaticWidth"; "cropperStaticHeight": "cropperStaticHeight"; "canvasRotation": "canvasRotation"; "initialStepSize": "initialStepSize"; "roundCropper": "roundCropper"; "onlyScaleDown": "onlyScaleDown"; "imageQuality": "imageQuality"; "autoCrop": "autoCrop"; "backgroundColor": "backgroundColor"; "containWithinAspectRatio": "containWithinAspectRatio"; "hideResizeSquares": "hideResizeSquares"; "allowMoveImage": "allowMoveImage"; "cropper": "cropper"; "alignImage": "alignImage"; "disabled": "disabled"; }, { "imageCropped": "imageCropped"; "startCropImage": "startCropImage"; "imageLoaded": "imageLoaded"; "cropperReady": "cropperReady"; "loadImageFailed": "loadImageFailed"; "transformChange": "transformChange"; }, never, never>;
                        ~~~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/image-cropper.module.d.ts:5:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.

5     static ɵfac: i0.ɵɵFactoryDeclaration<ImageCropperModule, never>;
                      ~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/image-cropper.module.d.ts:6:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵNgModuleDeclaration'.

6     static ɵmod: i0.ɵɵNgModuleDeclaration<ImageCropperModule, [typeof i1.ImageCropperComponent], [typeof i2.CommonModule], [typeof i1.ImageCropperComponent]>;
                      ~~~~~~~~~~~~~~~~~~~~~
node_modules/ngx-image-cropper/lib/image-cropper.module.d.ts:7:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectorDeclaration'.

7     static ɵinj: i0.ɵɵInjectorDeclaration<ImageCropperModule>;
                      ~~~~~~~~~~~~~~~~~~~~~

** Angular Live Development Server is listening on localhost:1411, open your browser on http://localhost:1411/ **
70% building 66/66 modules 0 active    
    ERROR in node_modules/ngx-image-cropper/lib/services/crop.service.d.ts:13:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.
    
    13     static ɵfac: i0.ɵɵFactoryDeclaration<CropService, never>;
                           ~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/services/crop.service.d.ts:14:22 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.
    
    14     static ɵprov: i0.ɵɵInjectableDeclaration<CropService>;
                            ~~~~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/services/cropper-position.service.d.ts:12:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.
    
    12     static ɵfac: i0.ɵɵFactoryDeclaration<CropperPositionService, never>;
                           ~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/services/cropper-position.service.d.ts:13:22 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.
    
    13     static ɵprov: i0.ɵɵInjectableDeclaration<CropperPositionService>;
                            ~~~~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/services/load-image.service.d.ts:15:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.
    
    15     static ɵfac: i0.ɵɵFactoryDeclaration<LoadImageService, never>;
                           ~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/services/load-image.service.d.ts:16:22 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectableDeclaration'.
    
    16     static ɵprov: i0.ɵɵInjectableDeclaration<LoadImageService>;
                            ~~~~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/component/image-cropper.component.d.ts:101:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.
    
    101     static ɵfac: i0.ɵɵFactoryDeclaration<ImageCropperComponent, never>;
                            ~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/component/image-cropper.component.d.ts:102:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵComponentDeclaration'.
    
    102     static ɵcmp: i0.ɵɵComponentDeclaration<ImageCropperComponent, "image-cropper", never, { "imageChangedEvent": "imageChangedEvent"; "imageURL": "imageURL"; "imageBase64": "imageBase64"; "imageFile": "imageFile"; "format": "format"; "transform": "transform"; "maintainAspectRatio": "maintainAspectRatio"; "aspectRatio": "aspectRatio"; "resizeToWidth": "resizeToWidth"; "resizeToHeight": "resizeToHeight"; "cropperMinWidth": "cropperMinWidth"; "cropperMinHeight": "cropperMinHeight"; "cropperMaxHeight": "cropperMaxHeight"; "cropperMaxWidth": "cropperMaxWidth"; "cropperStaticWidth": "cropperStaticWidth"; "cropperStaticHeight": "cropperStaticHeight"; "canvasRotation": "canvasRotation"; "initialStepSize": "initialStepSize"; "roundCropper": "roundCropper"; "onlyScaleDown": "onlyScaleDown"; "imageQuality": "imageQuality"; "autoCrop": "autoCrop"; "backgroundColor": "backgroundColor"; "containWithinAspectRatio": "containWithinAspectRatio"; "hideResizeSquares": "hideResizeSquares"; "allowMoveImage": "allowMoveImage"; "cropper": "cropper"; "alignImage": "alignImage"; "disabled": "disabled"; }, { "imageCropped": "imageCropped"; "startCropImage": "startCropImage"; "imageLoaded": "imageLoaded"; "cropperReady": "cropperReady"; "loadImageFailed": "loadImageFailed"; "transformChange": "transformChange"; }, never, never>;
                            ~~~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/image-cropper.module.d.ts:5:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵFactoryDeclaration'.
    
    5     static ɵfac: i0.ɵɵFactoryDeclaration<ImageCropperModule, never>;
                          ~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/image-cropper.module.d.ts:6:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵNgModuleDeclaration'.
    
    6     static ɵmod: i0.ɵɵNgModuleDeclaration<ImageCropperModule, [typeof i1.ImageCropperComponent], [typeof i2.CommonModule], [typeof i1.ImageCropperComponent]>;
                          ~~~~~~~~~~~~~~~~~~~~~
    node_modules/ngx-image-cropper/lib/image-cropper.module.d.ts:7:21 - error TS2694: Namespace '"/home/craftsmanship04/Desktop/Jaymit/JB/utilify-admin-client-v3/node_modules/@angular/core/core"' has no exported member 'ɵɵInjectorDeclaration'.
    
    7     static ɵinj: i0.ɵɵInjectorDeclaration<ImageCropperModule>;
                          ~~~~~~~~~~~~~~~~~~~~~
    

Date: 2022-07-27T10:46:39.868Z - Hash: e273d119ac8fb5a584af
1 unchanged chunks
chunk {default~invitations-invitations-module~sales-dashboard-sales-dashboard-module} default~invitations-invitations-module~sales-dashboard-sales-dashboard-module.js, default~invitations-invitations-module~sales-dashboard-sales-dashboard-module.js.map (default~invitations-invitations-module~sales-dashboard-sales-dashboard-module) 93.3 kB  [rendered]
chunk {default~modules-admin-admin-module~modules-public-public-module} default~modules-admin-admin-module~modules-public-public-module.js, default~modules-admin-admin-module~modules-public-public-module.js.map (default~modules-admin-admin-module~modules-public-public-module) 479 kB  [rendered]
chunk {email-templates-email-templates-module} email-templates-email-templates-module.js, email-templates-email-templates-module.js.map (email-templates-email-templates-module) 55.4 kB  [rendered]
chunk {main} main.js, main.js.map (main) 530 kB [initial] [rendered]
chunk {meter-lookup-meter-lookup-module} meter-lookup-meter-lookup-module.js, meter-lookup-meter-lookup-module.js.map (meter-lookup-meter-lookup-module) 60.5 kB  [rendered]
chunk {modules-admin-admin-module} modules-admin-admin-module.js, modules-admin-admin-module.js.map (modules-admin-admin-module) 11.3 MB  [rendered]
chunk {modules-public-public-module} modules-public-public-module.js, modules-public-public-module.js.map (modules-public-public-module) 69.5 kB  [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 141 kB [initial] [rendered]
chunk {pricing-pricing-module} pricing-pricing-module.js, pricing-pricing-module.js.map (pricing-pricing-module) 397 kB  [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 9.92 kB [entry] [rendered]
chunk {sales-dashboard-sales-dashboard-module} sales-dashboard-sales-dashboard-module.js, sales-dashboard-sales-dashboard-module.js.map (sales-dashboard-sales-dashboard-module) 8.62 kB  [rendered]
chunk {styles} styles.js, styles.js.map (styles) 1.21 MB [initial] [rendered]
chunk {suppliers-suppliers-module} suppliers-suppliers-module.js, suppliers-suppliers-module.js.map (suppliers-suppliers-module) 204 kB  [rendered]
chunk {system-users-system-users-module} system-users-system-users-module.js, system-users-system-users-module.js.map (system-users-system-users-module) 87.4 kB  [rendered]
chunk {tools-tools-module} tools-tools-module.js, tools-tools-module.js.map (tools-tools-module) 102 kB  [rendered]
chunk {utility-type-categories-utility-type-categories-module} utility-type-categories-utility-type-categories-module.js, utility-type-categories-utility-type-categories-module.js.map (utility-type-categories-utility-type-categories-module) 63.5 kB  [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 7.46 MB [initial] [rendered]
Time: 21596ms

ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1223:9575-9601
Can't import the named export 'ChangeDetectionStrategy' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1226:65-88
Can't import the named export 'ChangeDetectionStrategy' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1222:269-289
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1227:170-190
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1329:181-193
Can't import the named export 'CommonModule' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1331:12-24
Can't import the named export 'CommonModule' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1337:24-36
Can't import the named export 'CommonModule' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1225:18-27
Can't import the named export 'Component' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1222:241-256
Can't import the named export 'DomSanitizer' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1227:143-158
Can't import the named export 'DomSanitizer' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 825:32-44
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 826:34-46
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 827:31-43
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 828:32-44
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 829:35-47
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 830:35-47
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1288:22-33
Can't import the named export 'HostBinding' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1293:22-33
Can't import the named export 'HostBinding' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1310:22-34
Can't import the named export 'HostListener' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1313:22-34
Can't import the named export 'HostListener' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1316:22-34
Can't import the named export 'HostListener' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1319:22-34
Can't import the named export 'HostListener' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1322:22-34
Can't import the named export 'HostListener' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 315:18-28
Can't import the named export 'Injectable' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 516:18-28
Can't import the named export 'Injectable' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 774:18-28
Can't import the named export 'Injectable' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1234:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1236:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1238:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1240:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1242:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1244:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1246:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1248:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1250:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1252:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1254:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1256:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1258:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1260:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1262:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1264:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1266:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1268:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1270:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1272:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1274:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1276:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1278:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1280:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1282:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1284:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1286:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1291:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1296:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1223:9484-9491
Can't import the named export 'NgIf' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1334:18-26
Can't import the named export 'NgModule' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1298:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
[[39m31mERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1300:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1302:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1304:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1306:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1308:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1228:22-31
Can't import the named export 'ViewChild' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1231:22-31
Can't import the named export 'ViewChild' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 661:15-24
Can't import the named export '__awaiter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 682:15-24
Can't import the named export '__awaiter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1007:17-26
Can't import the named export 'isDevMode' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 312:135-153
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 513:157-175
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 771:145-163
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1222:302-320
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1328:149-167
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 314:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 515:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 773:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1224:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1333:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1223:29-52
Can't import the named export 'ɵɵngDeclareComponent' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 312:19-40
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 513:30-51
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 771:24-45
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1222:29-50
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1328:26-47
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 313:20-44
Can't import the named export 'ɵɵngDeclareInjectable' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 514:31-55
Can't import the named export 'ɵɵngDeclareInjectable' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 772:25-49
Can't import the named export 'ɵɵngDeclareInjectable' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1330:26-48
Can't import the named export 'ɵɵngDeclareInjector' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-image-cropper/fesm2015/ngx-image-cropper.mjs 1329:26-48
Can't import the named export 'ɵɵngDeclareNgModule' from non EcmaScript module (only default export is available)

Use MatomoModule and MatomoTracker in external module

Hi,

It's very often use case for global tools like WebAnalytics to create abstraction layer in app to do not stick to one solution. I try to do the same with Matomo module but I find it a bit cumbersome with current version. Issues I see is :

1. There is no way of providing configured abstract module which will internally use MatomoModule. My implementation was about to create WebAnalyticsModule.forRoot(config) with internally configuration of MatomoModule. What I tried was to provide MATOMO_CONFIGURATION separately and import MatomoModule only internally. The problem is that when I want to import my WebAnalyticsService which is facade for MatomoTracker to lazy loaded module I have to import WebAnalyticsModule again but it'll not work because MATOMO_CONFIGURATION has to be provided again otherwise I can't import MatomoModule again (it'll run init() method which needs MATOMO_CONFIGURATION). Solution would be to provide forRoot and forChild methods to MatomoModule

2. When I want to create WebAnalyticsService facade for MatomoTracker it can't be imported to services providedIn: 'root' because MatomoTracker is provided in module only (and needs MATOMO_CONFIGURATION). IMO it should be separate root service independent of MATOMO_CONFIGURATION, otherwise we need store support just to call tracker event in 'root' service.

Support to track events with string values

I currently it is only supported to track numeric values.
Matomo supports string values to.

Tracking Video

How can i make tracking video ?

Matomo initilization hangs when Heatmap & Session Recording plugin is enabled on Matomo server

When the the Heatmap & Session Recording plugin is enabled on the Matomo server, the ngx-matomo initialization method retrieves and attempts to execute a configs.php file from the Matomo server containing a single line of JavaScript which class a method of the Piwik object. This call tends to hang indefinitely, driving up CPU usage and crashing our Angular app. Indeed, if I simply try to inspect the Piwik object from the JavaScript console in Firefox while this is happening, that also hangs until Firefox allows me to forcefully stop the script; once I do that the details of the Piwik object do print to the console. This happens only when the plugin mentioned above is enabled.

Can't make it add the data-cookieconsent="statistics" attribute to the script tag

I want the generated script-tag to be extended by data-cookieconsent="statistics".
This allows to deny the script if statistic cookies are not allowed by the user (GDPR).

Support for Angular Universal

Hi.

ngx-matomo is very useful library, and will be very cool to fix the errors in console when I use it with Angular Universal (server side rendering, SSR).

I am wondering why, but still it's more or less working even with errors above.

Is there some huge problems to support SSR? If you just haven't a time to do this, I can made it by myself, you will need only to merge it.

Please let me know.

Exclude routes from automatic pageview tracking

Readme instructions for configuration with Tags?

I've gotten this embed code from our Matomo Manager, a custom Tag Manager container.

<!-- Company Name Tag Manager -->
<script type="text/javascript">
var _mtm = window._mtm = window._mtm || [];
_mtm.push({'mtm.startTime': (new Date().getTime()), 'event': 'mtm.Start'});
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.type='text/javascript'; g.async=true; g.src='https://company-matomo-server/js/container_4A3s32aA.js'; s.parentNode.insertBefore(g,s);
</script>
<!-- End Company Name Tag Manager -->

But the documentation are not clear how to configure npx-matomo with tags. I've tried this configuration but that actually froze the browser for some reason.

matomoConfig: {
    scriptUrl: 'https://company-matomo-server/js/container_4A3s32aA.js',
    trackers: [],
    routeTracking: {
      enable: true
    }
  }

Sure, I can figure out trackerUrl and siteId if thats needed. But I want to configure it the "correct" way. Is Matomo tags supported?

Is this repo still maintained ?

I am considering Matomo to monitor our Angular (11) app. This repository is the reference provided on their integration page.

Yet I seem to notice that:

• the last commit on master is 1+ year old
• the last commit on develop is 7+ months old
• the last merged PR is more than a year old (11 PR opened, most of them without reply)
• it is not clear whether milestone Release 1 will see any further progress

I understand that the maintainer may no longer be able to contribute to this project for free. But in that case, at least the readme should be updated with a clear mention at the top, indicating that contributors shouldn't waste their time.

Thanks

Enable routerTracking will throw error

Below is error message:
Unhandled Promise rejection: R3InjectorError(AppModule)[MatomoModule -> MatomoRouteTracker -> Router -> Router -> Router]: NullInjectorError: No provider for Router! ; Zone: <root> ; Task: Promise.then ; Value: NullInjectorError: R3InjectorError(AppModule)[MatomoModule -> MatomoRouteTracker -> Router -> Router -> Router]: NullInjectorError: No provider for Router! at NullInjector.get (core.js:11100) at R3Injector.get (core.js:11267) at R3Injector.get (core.js:11267) at R3Injector.get (core.js:11267) at injectInjectorOnly (core.js:4751) at Module.ɵɵinject (core.js:4755) at Object.MatomoRouteTracker_Factory [as factory] (ngx-matomo.js:1919) at R3Injector.hydrate (core.js:11437) at R3Injector.get (core.js:11256) at new MatomoModule (ngx-matomo.js:1961) NullInjectorError: R3InjectorError(AppModule)[MatomoModule -> MatomoRouteTracker -> Router -> Router -> Router]: NullInjectorError: No provider for Router! at NullInjector.get (http://localhost:4200/vendor.js:27658:27) at R3Injector.get (http://localhost:4200/vendor.js:27825:33) at R3Injector.get (http://localhost:4200/vendor.js:27825:33) at R3Injector.get (http://localhost:4200/vendor.js:27825:33) at injectInjectorOnly (http://localhost:4200/vendor.js:21309:33) at Module.ɵɵinject (http://localhost:4200/vendor.js:21313:61) at Object.MatomoRouteTracker_Factory [as factory] (http://localhost:4200/vendor.js:233002:308) at R3Injector.hydrate (http://localhost:4200/vendor.js:27995:35) at R3Injector.get (http://localhost:4200/vendor.js:27814:33) at new MatomoModule (http://localhost:4200/vendor.js:233044:27)
Use npm install is ok for me but use yarn install will throw this error

npm warn for angular > 6.0.0

H Arnaud,

We recently updated our project to the newest version and during installation we are getting npm warn:

npm WARN [email protected] requires a peer of @angular/core@>=5.0.0 <6.0.0 but none is installed. You must install peer dependencies yourself

Our angular version is -> "@angular/core": "6.0.7"

Is it possible to fix thix warning?

Add to Matomo integration page

Hi,

Thanks for creating this library. I have added it to the Matomo integration page:
https://matomo.org/integrate/

removeEcommerceItem does not exist

Hi,

it seems that the removeEcommerceItem function is not implemented. Could you add it?

Or is there a reason why it's not implemented? (addEcommerceItem and trackEcommerceCartUpdate are there)

Regards,

Philipp

Error during initialization

Hello Arnaud,

Thanks for your awesome matomo wrapper.
I'm trying to use it but I have a small error when the matomo code is injected.

I'm getting GET https://analytics.changr.com/piwik.js 0 ()

I used the injector as following:
this.matomoInjector.init('https://analytics.changr.com/', environment.MATOMO_SITE_ID);

Do you have any idea of the origin of my issue?

Thanks a lot,
Gabriel

Add support for consent management

Tracker get functions return incorrect data

Following tracker methods return incorrect data:

• getPiwikUrl
• getCurrentUrl
• getLinkTrackingTimer
• getVisitorId
• getVisitorInfo
• getAttributionInfo
• getAttributionCampaignName
• getAttributionReferrerTimestamp
• getAttributionReferrerUrl
• getUserId
• getCustomVariable
• getCustomDimension
• hasCookies

HttpRequest for trackerUrl and siteId

Hi there
I am currently migrating from matomo 0.1.4 to 1.0.1. In my project we get the trackerUrl and the siteId via an HttpRequest. So far i could solve this with the MatomoInjector. How can I integrate this into the forRoot? Is there any idea?

All requests to piwik/matomo are blocked by ad blockers

Trying to implement this in my angular application, but I was only able to do it after disabling my ad blocker.

I am using ublock.

Does any body know how to track the visit without having to disable ad blockers?

I saw some threads about this, in the matomo repo, but nothing helped me since I am using ngx-matomo.

thanks

trackSiteSearch does not add search count when count is 0

When using the trackSiteSearch method, If we pass ) the method won't add search count to matomo url because of the inner logic:

The logic used is:

 if (!!resultsCount) {
                args.push(resultsCount);
  }

In the above code, if condition never gets satisfied when resultsCount is 0 beacuse:

if (0) {
//never comes here
console.log('HI')
}

So you can use some thing like:

if( resultsCount !== undefined&& typeof resultsCount === "number") {
   args.push(resultsCount);
}

I have created a pull request for this: Here

Option to disable tracking when Angular is in dev mode

Hi,

Could it be possible to add an option (or make it a default behaviour) that stops tracking when Angular app is in dev mode ? Of course all trackPageView() calls can be surrounded by a test if (! isDevMode()) but this impacts readability, and it seems quite natural not to track page views generated by the developer's work.

What makes me ask for this feature is the following issue I ran into: running e2e tests with Protractor triggers hundreds of Matomo events. In such a case, IP / hostname filtering in Matomo settings is not always a good solution because it requires extra attention and frequent adjustments (since IP may change, especially when working at home), and may also be unavailable to the developer depending on who runs Matomo.

Thanks for your consideration,
Mathias

Does it track routing

Does it automatically tracks angular routing? If not by default, how do you do it (would be a nice add to the README).