We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have cloned the repository successfully, when l try to run the dependencies l get npm install
changed 1 package, and audited 1408 packages in 6s
238 packages are looking for funding run npm fund for details
npm fund
8 vulnerabilities (2 moderate, 6 high)
To address all issues (including breaking changes), run: npm audit fix --force
Run npm audit for details.
npm audit
Seems the npm audit fix --force doesn't solve the problem either. Some l am stuck here.
The text was updated successfully, but these errors were encountered:
It could be a version thing.
I noticed in the audit that ...
@angular-devkit/build-angular <=14.2.12 || 15.0.0-next.0 - 15.2.10 || 16.0.0-next.0 - 16.2.12 || 17.0.0-next.0 - 17.3.1
and the version that is used nowadays is 20.
The app needs to be updated to use modern versions of node.js
also this...
npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: 'angular-app@0.0.0', npm warn EBADENGINE required: { npm: '>=8.0.0 <9.0.0', node: '>=16.0.0 <17.0.0' }, npm warn EBADENGINE current: { node: 'v22.2.0', npm: '10.8.1' } npm warn EBADENGINE }
Sorry, something went wrong.
No branches or pull requests
I have cloned the repository successfully, when l try to run the dependencies l get
npm install
changed 1 package, and audited 1408 packages in 6s
238 packages are looking for funding
run
npm fund
for details8 vulnerabilities (2 moderate, 6 high)
To address all issues (including breaking changes), run:
npm audit fix --force
Run
npm audit
for details.Seems the npm audit fix --force doesn't solve the problem either. Some l am stuck here.
The text was updated successfully, but these errors were encountered: