When updating the Angular update tool suggested me to migrate to the new build system => I accepted
Run npm update to update other libs & fix some vulnerabilities spot by npm audit
Changed angular-tag-manager peer dependencies from ^17.0.3 to ^18.0.0
Other modification suggested:
While updating I've some deprecated libraries used and a unit test where the expectation is never reached.
I want to keep this PR light and don't want it to be blocked because of some refactoring stuff, so I've created branches on my fork.
They all are based on this Angular 18 migration PR, so if you are OK after this branch is merged I can put those 3 PR.
thank you @guillaume-moreau , PR has been merged and the library has been published , feel free to create pr for your other branches, your contributions are welcome!
Hi @mzuccaroli
This PR is for #197
What I did:
npm update
to update other libs & fix some vulnerabilities spot bynpm audit
^17.0.3
to^18.0.0
Other modification suggested:
While updating I've some deprecated libraries used and a unit test where the expectation is never reached.
I want to keep this PR light and don't want it to be blocked because of some refactoring stuff, so I've created branches on my fork. They all are based on this Angular 18 migration PR, so if you are OK after this branch is merged I can put those 3 PR.
Remove protractor https://github.com/guillaume-moreau/angular-google-tag-manager/tree/feature/remove-protractor
Replace codelyzer by eslint https://github.com/guillaume-moreau/angular-google-tag-manager/tree/feature/replace-codelyzer
Test with expectation never reached https://github.com/guillaume-moreau/angular-google-tag-manager/tree/feature/test-without-expectation
I'm available for any suggestion/remarks !
Thank you :)