Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 days ago.
Improve this question
https not defined
Even after adding
const https=require("https");
The issue ain't getting resolved .
Does http:// work? If it does, the site you are attempting to connect to might not be secure. https:// only works if the site information is encrypted.
You gave const https=require("https");, but I don't know the context of what you are attempting to use it for, so this is hard to answer.
Are you using that variable out of scope?
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 days ago.
Improve this question
I am trying to establish webRtc connection between 2 Firefox browsers (browser1 and browser2) on a local computer (javascript). The connection is established, but when I call RTCPeerconnection.addTrack() from the browser1, there is no 'track' event fired on the browser2 (peer). I am trying to understand the reason. The question is: at what point I should call RTCPeerconnection.addTrack() - when RTCPeerconnection has just been created, or when my computer has got answer to its offer , or it does not matter ? How can I deal with the problem (track is not sent actually, sent, but not received, any other reasons) ?
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 hours ago.
Improve this question
please solve this error
This Serverless Function has crashed.
Your connection is working correctly.
Vercel is working correctly.
500: INTERNAL_SERVER_ERROR
Code: FUNCTION_INVOCATION_FAILED
ID: bom1::zcvsk-1676826098000-9c8a6550e562
If you are a visitor, contact the website owner or try again later.
If you are the owner, learn how to fix the error and check the logs.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 days ago.
Improve this question
I have tried to send a message to the "shopping bot" after I declared it and its config in the main.ts, but I am getting an error that the shopping bot resource does not exists.
I found the Solution it was a versioning problem with the lex dependancy.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 years ago.
Improve this question
i am using this lib the small data process but large data not process it goes to server crash
try catch method also be user but it not catch error
node make report.json file
it lib issue any else
Memory limit? Try launch nodejs with --max-old-space-size=4096 key. It set memory limit to 4GB from default ~1.4GB.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 6 years ago.
Improve this question
I've implemented the router and everything works (navigation etc.) but how can I make sure that when I want to go to http://myapp.dev/members that the url is handled by react (router)? When I type that URL in my browser now, nothing happens, because the /members doesnt exist (backend)
You need to redirect your backend to wherever your react application is. react-router themselves have it in their documentation. If you're on nginx, use a try_files rule to try, see if it exists, and if not, fire back to wherever your react app is.
The same goes for Apache using rewrite rules.
Both are actually very well documented within the doc.