Angular-fullpage tied to Angular 12

[ArjanKw]

Thank you for updating the project and to provide example projects. I'm able to get it to work with Angular 19 and standalone components by copying the dist folder of your project into my project and reference that. When I’m using the 0.1.5 npm package I’m not able to install it, as (if I'm correct) the dependencies are set to Angular 12.

In the angular-fullpage package.json I see the following:

"dependencies": {
    "@angular-devkit/build-angular": "12.0.0",
    "@angular/common": "12.0.0",
    "@angular/core": "12.0.0",
    "@angular/cli": "12.0.0",
    "@angular/compiler": "12.0.0",
    "@angular/compiler-cli": "12.0.0",
    "fullpage.js": "4.0.35"
  },

This (I presume) leads to a whole list of errors when I execute npm i:

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@angular-devkit/build-angular@12.0.0',
npm warn EBADENGINE   required: {
npm warn EBADENGINE     node: '^12.14.1 || ^14.0.0',
npm warn EBADENGINE     npm: '^6.11.0 || ^7.5.6',
npm warn EBADENGINE     yarn: '>= 1.13.0'
npm warn EBADENGINE   },
npm warn EBADENGINE   current: { node: 'v22.14.0', npm: '10.9.2' }
npm warn EBADENGINE }

I assume this will be fixed by updating the package.json to look like this:

"dependencies": {
    "@angular-devkit/build-angular": ">12",
    "@angular/common": ">12",
    "@angular/core": ">12",
    "@angular/cli": ">12",
    "@angular/compiler": ">12",
    "@angular/compiler-cli": ">12",
    "fullpage.js": "^4.0.35"
  },,
  "devDependencies": {
    "ng-packagr": ">=12",
    "ts-node": ">=8.0.0",
    "typescript": ">=4.2.3"
  }

See PR #143

[alidihaw]

Npm warn not stopped when install package.json

i has try angular 12-19 using npm package directly,

Wait this pr approved
#145

[ArjanKw]

Thank you both, the new 0.1.6 npm package fixes the problems, the dependency on Angular 12 is lifted, the imports work again and the Node compatibility warnings are gone.

[alvarotrigo]

@ArjanKw thanks to you for pointing it out! 👍