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
Receiving this error suddenly, did not install any new dependancies. Was working fine yesterday. Anyone know what the issue is suddenly?:
remote: remote: NPM_CONFIG_LOGLEVEL=error remote: NODE_VERBOSE=false remote: NODE_ENV=production remote: NODE_MODULES_CACHE=true remote: remote: -----> Installing binaries remote: engines.node (package.json): unspecified remote: engines.npm (package.json): unspecified (use default) remote: remote: Resolving node version 16.x... remote: Downloading and installing node 16.15.1... remote: Using default npm version: 8.11.0 remote: remote: -----> Restoring cache remote: Cached directories were not restored due to a change in version of node, npm, yarn or stack remote: Module installation may take longer for this build remote: remote: -----> Installing dependencies remote: Installing node modules remote: npm ERR! code ERESOLVE remote: npm ERR! ERESOLVE could not resolve remote: npm ERR! remote: npm ERR! While resolving: [email protected] remote: npm ERR! Found: [email protected] remote: npm ERR! node_modules/next remote: npm ERR! next@"^11.0.0" from the root project remote: npm ERR! peer next@">=10.2.0" from [email protected] remote: npm ERR! node_modules/eslint-config-next remote: npm ERR! dev eslint-config-next@"^11.0.1" from the root project remote: npm ERR! remote: npm ERR! Could not resolve dependency: remote: npm ERR! peer next@"^10.0.8" from [email protected] remote: npm ERR! node_modules/next-page-tester remote: npm ERR! dev next-page-tester@"^0.26.1" from the root project remote: npm ERR! remote: npm ERR! Conflicting peer dependency: [email protected] remote: npm ERR! node_modules/next remote: npm ERR! peer next@"^10.0.8" from [email protected] remote: npm ERR! node_modules/next-page-tester remote: npm ERR! dev next-page-tester@"^0.26.1" from the root project remote: npm ERR! remote: npm ERR! Fix the upstream dependency conflict, or retry remote: npm ERR! this command with --force, or --legacy-peer-deps remote: npm ERR! to accept an incorrect (and potentially broken) dependency resolution. remote: npm ERR! remote: npm ERR! See /tmp/npmcache.24uzX/eresolve-report.txt for a full report. remote: remote: npm ERR! A complete log of this run can be found in: remote: npm ERR! /tmp/npmcache.24uzX/_logs/2022-06-02T23_[31](https://github.com/mattfrancis888/bobbyhill/runs/6717802139?check_suite_focus=true#step:3:32)_12_[68](https://github.com/mattfrancis888/bobbyhill/runs/6717802139?check_suite_focus=true#step:3:69)3Z-debug-0.log remote: remote: -----> Build failed remote: remote: We're sorry this build is failing! You can troubleshoot common issues here: remote: https://devcenter.heroku.com/articles/troubleshooting-node-deploys remote: remote: Some possible problems: remote: remote: - Node version not specified in package.json remote: https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version remote: remote: Love, remote: Heroku remote: remote: ! Push rejected, failed to compile Node.js app. remote: remote: ! Push failed remote: Verifying deploy... remote: remote: ! Push rejected to bobbyhill-uat. remote:
name: Deploy on: push: branches: - development jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: akhileshns/[email protected] # This is the action with: heroku_api_key: ${{secrets.HEROKU_API_KEY}} heroku_app_name: "myproject-uat" #Must be unique in Heroku heroku_email: "[email protected]"```
The text was updated successfully, but these errors were encountered:
Facing the same issue but with React versioning. Solutions might be simple. Adding : npm install --legacy-peer-deps npm audit fix --force
npm install --legacy-peer-deps
npm audit fix --force
Sorry, something went wrong.
Try deleting the package-json.lock then npm install to regenerate it.
package-json.lock
npm install
No branches or pull requests
Receiving this error suddenly, did not install any new dependancies. Was working fine yesterday. Anyone know what the issue is suddenly?:
dev.yaml
The text was updated successfully, but these errors were encountered: