pusher-js | Pusher Javascript library | Runtime Evironment library

Let's say I have a vue client trying to receive an event from a private channel using pusher services.

This client autenticates using pusher auth secuence:

Here are the docs: https://pusher.com/docs/channels/server_api/authenticating-users/

Seems I need to provide an endpoint on my server in order to autenticate the user.

So, as the docs says, since my server is in a different domain to the front-end app, I need to use CORS or JSONP, I choose JSONP.

My server (backend) is made in Django using django-rest-framework and it provides an endpoint that is responsible to process the socket_id, the channel_name and the callback that the pusher-js (which is a pusher frontend library) generates.

Something alike to a javascript code is sent to the frontend, so the response needs to be content-type:application/javascript.

In order to test the event, I made a simple python script which I will later integrate to my bussiness logic. This script is the responsible to trigger the event.

The problem: The main problem is the event never arrives. I looked up into the web-console (frontend) to check the correct function of the requests. The ws protocol requests responds with status 101 and the endpoint /auth/pusher with status 200. So they seem to work correctly.

• Here is my Django /auth/pusher endpoint:

...

I'm using

• Laravel: 8.54
• Laravel Sanctum: 2.11
• Pusher Php Server: 7.0
• NuxtJs: 2.15.7
• pusher-js: 7.0.4
• laravel-echo: 1.11.3

Event Class

I'm aware of many posts regarding these warnings in Chrome dev tools. For all of them, the solution is to turn off notifications "Enable javascript source maps" and "Enable CSS source maps".

What I want to know is how to FIX this and what is the reason under the hood that causes these warnings.

I'm currently developing a Vue JS app that uses Twilio Js SDK and I'm getting tons of warnings when the app is built in stage mode by using sudo npm run build -- --mode staging

Any advice will be appreciated.

I have a app that is currently deployed on heroku and working perfectly fine. I created a new heroku app and tried to run the same branch. I installed nodejs and all the configuration is the same but for some reason the build is failing at heroku-postbuild: "ng build --prod". It works fine on the previous instance I have on heroku but wont work on the new one. I don't know what i am missing as the information on the error is minimal. I am attaching my package.json as well as the error message I get. any help will be appreciated and let me know if you need me to upload anything else.

package.json

I have an app that works using Laravel on the backend, and React on the frontend.

We are using beyondcode/laravel-websockets to broadcast websocket messages from the Laravel server to a React client.

React is able to get the message using the following code:

Am using Laravel Websockets Package for real time application on localhost everything work perfect but on production i have some issues.

I run websockets through supervisor on centos, i can can access to Laravel websockets Debug Dashboard and connect successfully which mean that laravel websocket run in the background.

when I Triger an event i get error Failed to connect to Pusher.

Route to test event

I am new to dealing with something like a supervisor on the CentOS server I ask for help to solve this issue.

I am facing issue with Laravel websockets (beyondco). In localhost, everything works well but in production, I started to install the supervisor package for centos 7 and I follow the steps in the documentation step by step.

After I install the supervisor package am going to directory /etc/supervisord.d and create websockets.conf and vim the file with the following:

websockets.conf (i guess that this file has misconfiguration)

We have two projects that share a API wrapper library (that we created) that makes use of the pusher-js library for websocket communication.

The API wrapper was originally built for the web version project built on NextJS, but now we wish to include it in our new React Native project. The issue is inside the API wrapper where we instantiate pusher, we import pusher from 'pusher-js whereas for this to work on React Native we need to import pusher from 'pusher-js/react-native. This lib is obviously unaware of the outer usage of who installs it and just sets these things up as a convenience wrapper.

How could this be achieved within either the mobile project or should this be setup within the API lib? I've looked into module resolution via a babel plugin but not sure how this would be setup for this instance.

Every video I've seen regarding to showing or hiding a div, is quite not effective at all if you're making use of a state that's based on true or false, thus when a button is clicked through the .map() all elements that are hidden would be shown, therefore it wouldn't be in great use of all, I guess that's why the element's index should be in use to determine which element should shown or hidden right?

Scenario

So I'm building a social platform for a learning experience, where I map through all my posts in an array, once I click my comment Icon, the comments should be shown for that post, but unfortunately I'm unable to find a solution regarding to the use of functional components.

this is what I have: