It is said here Cannot deploy Next.js to Netlify. Deploy failed due to an error in #netlify/plugin-nextjs plugin :
"Removing the #netlify/plugin-nextjs from the plugins tab on Netlify fixed the issue for me. I removed the plugin and triggered a new deploy."
I can't see any "plugins tab on Netlify". Where is it ?
Related
I have an AWS Amplify application (next.js, node v16.18.1) with two builds (dev & prod branch). One week ago the prod build failed with the following error message without any code being modified:
!!! CustomerError Framework Web not supported
The dev build still works. To check I've created a branch from dev called test and ran a build. This build failed with the same error as above.
There a no warnings or such in the AWS Amplify build log.
I've deleted the AWS Amplify app, created a new one resulting in the same error. I've deleted individual builds in the AWS Amplify app all resulting in the same error for the prod or test branch (which is a clone of the dev branch) while dev is building successfully in all scenarios.
It appears the branch is mistakenly being detected as web which is what is used for applications that use frameworks like React or Angular. Try running this command to update your branch's framework to Next.js - SSR:
aws amplify update-branch --app-id <value> --branch-name <value> --framework 'Next.js - SSR'
Source
I am trying to connect our Team City and our GitLab. I configured all "Version settings" as it was described in the manual:
The root have default brunch as some private brunch that I created.
When I press the "Commit current project settings" I het this error:
Error while committing settings change 'TeamCity change in 'NetSuite-AI-Solutions / cxi-recommender' project: commit current project settings': Push failed, status: REJECTED_OTHER_REASON, message: hook declined
I checked that our GitLab has no hooks. I even tried to remove protection from master brunch, but this does not solve the problem.
What else can I do to fix this issue? How I get more informative Team City log?
When the release pipeline run end up with this error
RangeError [ERR_INVALID_OPT_VALUE]: The value "4294967295" is invalid for option "size".
I don't know what means this error
task failed
Log of the task failed when release run
Same issue for me using Web Deploy to a nodejs app service.
Web Deploy worked at first, until we added some packages in our package.json (e.g. "#fortawesome/free-brands-svg-icons")
Then our release pipeline suddenly outputs "64-bit = +" in the deployment log.
If we remove the packages, the "64-bit = +" is gone, and our Web Deploy works again.
Image of log from Release pipeline
Not sure how to resolve it, but in our case we used Zip Deploy instead like #Ari Gunawan recommended.
I had the same issue when trying to deploy a node app to Azure App Service from release pipeline. Not sure what the error means as there are no further details about it but I resolved it by using "Zip Deploy" deployment method and "Continue on error"
I am trying to edit some docs on github, here are my instructions:
Clone the repo
Create a virtual environment
Install dependencies
Start a local server
I am able to 1 and 2 no problem, and 3 installs: mkdocs and mkdocs-material
I run into an issue on #4 with an error:
"ERROR - Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav' instead.
Aborted with 1 Configuration Errors!"
The MkDocs website does state this:
"Breaking change: the pages config option that was deprecated for a very long time now causes an error when used (#2652)
To fix the error, just change from pages to nav."
I am not a dev, so not sure what changing pages to nav means. There are some files named pages, but changing to nav would be nav(2).
How would I fix this?
TIA!
So MkDocs no longer supports the 'pages' tag on generating the site. The replacement for it is called 'nav'.
So all you have to do generally is replace 'pages' in your mkdocs with 'nav' and that should fix it
I know that there's couple posts like this one, but solution of any of them works for me.
Here is what I receive when I go for git push heroku master:
Please support. Ignoring node_modules is not working.
Docpad app - package.json file is updated according to docpad's manual.
I also have Procfile set up as in the link above.
PS. I have tried to deploy docpad app via openshift, but while Im going with manual from http://docpad.org/docs/deploy/ I receive error at step 5.
The application 'appname' is configured for git reference deployments but the
artifact provided ('https://github.com/myusername/appname#master') is a url.
Please provide a git reference to deploy (branch, tag or commit SHA1) or
configure your app to deploy from binaries with 'rhc configure-app appname
--deployment-type binary'.
If I configure myapp to deployment-type binary it isnt working neither.
The plugin which heroku tries to install returned 404 and the installation fails due to that.
Verify that the plugin is indeed public and not something you have wrote or used locally.
There is no package with this name hosted on the registry you use.
Remove the line with "docpad-plugin-blah": "2" from your package.json file. That line was provided in the docs simply to show you how to install plugins, but there's no such plugin as blah.
"dependencies": {
"docpad": "6"
},
I strongly recommend that you read through the Getting Started on OpenShift to get an overview of the development workflow using Git.
That being said, and if you really meant to use git reference deployments and you know why you are using them, then read through the Managing Deployments section on the developers page of OpenShift and find out how to properly set up git reference deployments. For instance, 'https://github.com/myusername/appname#master' is not a valid git url and therefore it cannot be cloned.