I'm using Hapi to run an API testing deployment on different platforms.
First of all I tried Heroku and everything worked fine.
Then I tried to run on Azure Web Apps and it failed with an error
"Hello all.
I'm using Hapi to run an API testing deployment on different platforms.
First of all I tried Heroku and everything worked fine.
Then I tried to run on Azure Web Apps and it failed with an error that error:
First I thought it was some error particular to Azure, but now I'm trying to run on Repl.it and got caught with the same error.
Is it specific to Hapi?
I'm using Yarn to manage my dependencies.
I faced the same issue when I tried to test Hapi on my cloud container before.
For my case, there has compatibility issue between Hapi version (I used v19.1.1) and Node version (my server default version 10.16.0).
The issue is resolved after I upgrade the Node version to 12.16.1 LTS.
Related
need help. does anybody faced this issue while deploying code on server? Everything is working fine on local.
ReferenceError: globalThis is not defined
Server setup: ECS fargate- docker container with Bitbucket pipeline
Node: 10 defined in docker
Server is keeps getting reloaded because of this issue.
globalThis is only available in Node v12 and newer so you cannot use it if you are using Node v10.
If it's your own code, you can use global instead, which is the same thing.
If the error is not coming from your own code, you'll have to upgrade your node version or get rid of the dependency it's coming from.
Note than Node v10 is no longer supported. It hasn't received any updates, including security updates, in a long time. If at all possible, you should upgrade to a supported version of Node (at the time of this writing, 18 is the latest LTS release).
Ive scoured to web with no avail..
noob here as well... sorry im still learning
App Dependencies are all out of date... I honestly dont know how to go about updating them yet
System Meteor version is 2.9.1
App Meteor version is 1.4.4.1
when I run Yarn Start, Meteor Tools starts download and extracting. well, it never finishes extracting, even if i leave it for hours.
Works locally no problems but when running on the AWS server or Digital Ocean droplets, both get stuck on Meteor Tools Extracting
I attempted to remove meteor and reinstall meteor globally. Didn't touch anything inside the app as i dont want to break the app. Tried running
meteor update
only for it to freeze on meteor tools extracting. Also tried
meteor update --patch
only to have it freeze as well.
I am using the LTS version of NodeJS. The problem started with version node-v16.18.0-x64 and did continue with node-v18.12.0-x64.
What I am doing:
Developing Playwright test. I ran the test and NodeJS was working. After one minute, I rerun the test and NodeJS is no longer recognized in my OS.
The issue appears when I am using Cypress, so I think the issue is not related to the technology that I am using.
I checked the environment variable: It is there.
The workaround I am doing is to uninstall the NodeJS from the control panel and install it again. There is an option to repair the NodeJS installation. But when I try to use it, I receive an error message that the NodeJS is not installed on this OS.
I have made a REST API for my chat-app. I am trying to deploy it on Heroku, the API runs perfectly with "Heroku local". I have trying to find a way to solve this for 2 months now.
I have found a similar issue Github Issue.
The issue is supposedly patched in Node.js v12.1.0.
Could you try updating your Node.js version to atleast v12.1.0 if your version is earlier.
what does these command means?
Secondly my nodejs RestAPI is working fine with local machine - but not working once i deploy it to server using nodejs cpanel.
Local postman
while in actual server getting "Cannot GET /apps/api/product/all" -- where my domainName/apps represents "Application URL" in the Cpanel.
little advice....push your project to git then pull it to your server. all dependencies on your machine will be ignored then in the server you can run install updated packages and compatible with your servers Operating system then start the server. fixes most of the version dependency problems you will keep facing. This is the ideal concept not a straight answer