Update to support angular 18

[gwentey]

Currently version 3.1.0 is not working with angular v18.

npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: [email protected] npm error Found: @angular/[email protected] npm error node_modules/@angular/common npm error @angular/common@"18.2.13" from the root project npm error npm error Could not resolve dependency: npm error peer @angular/common@"14 - 17" from [email protected] npm error node_modules/angular-tabler-icons npm error angular-tabler-icons@"3.1.0" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error

[pierreavn]

Hi, please use latest version of the package:
npm install [email protected]

[gwentey]

Hello,
I already tried but the lastest version use : linkedSignal
and it doesn't exist in angular 18

[INFO] ./node_modules/angular-tabler-icons/fesm2022/angular-tabler-icons.mjs:64:16-28 - Error: export 'linkedSignal' (imported as 'linkedSignal') was not found in '@angular/core'

thanks

[molinet]

Same problem here, none of the 3.X versions work with angular 18 as they all cause that same error.

[demotey]

Same problem .... Same problem... and I don't know what to do my application in production has been down for 2 days...

[the-ult]

Latest version is indeed for angular >= 19
Should have made that more clear.

@pierreavn, should I add this to the readme (and supported versions).
And maybe release a 4.x -> Breaking change?

With Angular 18, you should downgrade.

With 3.1.x you can use the allowVersions in your package.json when using pnpm

For example:

"pnpm": {
    "peerDependencyRules": {
      "allowedVersions": {
        "angular-tabler-icons>@angular/common": "18",
        "angular-tabler-icons>@angular/core": "18"
      }
    }
  },

With npm this should work:

"overrides": {
  "angular-tabler-icons": {
    "peerDependencies": {
      "@angular/common": "18.x",
      "@angular/core": "18.x"
    }
  }
}

Or use npm i --legacy-peer-deps (for now)

[gwentey]

Latest version is indeed for angular >= 19 Should have made that more clear.

@pierreavn, should I add this to the readme (and supported versions). And maybe release a 4.x -> Breaking change?

With Angular 18, you should downgrade.

With 3.1.x you can use the allowVersions in your package.json when using pnpm

For example:

"pnpm": {
    "peerDependencyRules": {
      "allowedVersions": {
        "angular-tabler-icons>@angular/common": "18",
        "angular-tabler-icons>@angular/core": "18"
      }
    }
  },

With npm this should work:

"overrides": {
  "angular-tabler-icons": {
    "peerDependencies": {
      "@angular/common": "18.x",
      "@angular/core": "18.x"
    }
  }
}

Or use npm i --legacy-peer-deps (for now)

It works ! thanks

[pierreavn]

Latest version is indeed for angular >= 19 Should have made that more clear.

@pierreavn, should I add this to the readme (and supported versions). And maybe release a 4.x -> Breaking change?

With Angular 18, you should downgrade.

With 3.1.x you can use the allowVersions in your package.json when using pnpm

For example:

"pnpm": {
    "peerDependencyRules": {
      "allowedVersions": {
        "angular-tabler-icons>@angular/common": "18",
        "angular-tabler-icons>@angular/core": "18"
      }
    }
  },

With npm this should work:

"overrides": {
  "angular-tabler-icons": {
    "peerDependencies": {
      "@angular/common": "18.x",
      "@angular/core": "18.x"
    }
  }
}

Or use npm i --legacy-peer-deps (for now)

Indeed you right y'all.

I never used npm overrides, @the-ult if you have time, could you do a PR explaining this in README? it would be awesome.

[the-ult]

I'll try to make some time during the holidays/vacation.
Add some tests and improve readme