passport | Simple , unobtrusive authentication for Node.js | REST library

I have a Json File which contains blog, when I am passing

I'm in the process of developing a Client Registration page for a travel agent. The client needs to save the passport number as a record in the MySQL database. I would like to know the data type ideal for mentioning in the migrations page for storing a Passport number. Usually, a passport number contains one or two English Letters and a few digits.

I see in a blog (here) about Authentication in React with JWT, this setup: access token expiry is 15 minutes , refresh token expiry is 1 month; every 10 minutes the client calls the /refreshToken endpoint, to check if refreshToken is still valid (otherwise the user is shown the login screen).

On the server, the /refreshToken endpoint correctly checks that the refreshtoken is not expired, that the user with the id in refreshtoken payload is still existing and valid (i.e.: the passed refreshToken is present in his refreshTokens array). If everything's fine, a new access token is generated, and sent back with the response.

So far so good. But, before returning the response, a new refreshToken is generated, too, and replaced to the old one into users's refreshTokens array... I think this strategy is flawed, since this way the user will never see his login to expire, even after refresh token (one month in this example) will be overdue...

I did make some tests (lowering the 1 month value to 30 minutes), and effectively the user authorization never expires... Forcing a logout of the user deleting his refreshTokens array obviously works fine, but I'd expect a logout when the refresh token expires by age.

I ask if my understanding is correct (the refreshToken endpoint on the server should not refresh the refresh token, but the access token only), or if I miss something.

UPDATE after @Ghero comment: I see your point... But why to refresh a token if not to update it's expiry?
However, the blog's code used to renew the refresh token:

I have upgraded my angular to angular 13. when I run to build SSR it gives me following error.

I have following package.json

I'm trying to integrate login using Snapchat to my application. In order to do that I need to add an authorization bearer to the callback request to my application so I can verify the client. According to Snapchat guide I need to use _qs or Axios to create the request:

I've deployed my MERN app on Heroku and everything was fine until I realized an issue every time I refresh the page or try to access a route from the address bar. While navigation through React Router links is fine, trying to go directly to a route from URL address bar or refreshing the page is causing the app to break and sending server responses directly to the browser instead of rendering the component - to clarify: if a given route was supposed to make a GET request and display some data, the actual JSON is displayed on-screen.

As far as I've checked, this is happening only on components that make a GET request.

server.js

I'm currently developing an app in Laravel and deploying it in Heroku.

I get this error when pushing:

symfony / polyfill-ctype v1.24.0 requires php >= 7.1

Anyone knows how to solve this?

The truth is that I investigated but I couldn't think of what to do. I already tried running composer update and there is no solution either.

Im using Laravel Framework 8.78.1

I'm using node.js to code a simple login/ sign up program that stores the account details (username, email, and password) on a MongoDB database. I've made sure I've downloaded MongoDB correctly, but I can't figure out what's wrong with my code... there are no errors thrown but the name, email, and hashedPassword aren't being inserted into the users database.

Here's my code from my server.js file: