error-handler | Provides tools to manage errors and ease debugging PHP code | Web Framework library

Express doesn't have a chance here because you're serializing the error object yourself and sending that. So, you've taken over that job from Express. The stack will still be in the error object itself. That comes from the source of the error.

If you want to send the error stack in non-production mode, I would propose a modification of your proposal like this:

You must be providing old token in the body. Try to authenticate again and then provide new token. It may work.

• logger: a person who receives the log string, sorts it by a predefined level, then uses his own handler if any to process the log and, by default passes the log to his superior.
• root logger: the superior of superiors, does all the things that a normal logger does but doesn't pass the received log to anyone else.
• handler: a private contractor of a logger, who actually does anything with the log, eg. formats the log, writes it to a file or stdout, or sends it through tcp/udp.
• formatter: a theme, a design that the handler applies to the log.
• basicConfig: a shortcut way to config the root logger. This is useful when you want him to do all the job and all his lower rank loggers would just pass the log to him.
  With no argument, basicConfig sets root logger's level to WARNING and add a StreamHandler that output the log to stderr.

1. You created a format and used a shortcut basicConfig to config the root logger. You want the root logger to do all the actual logging things
2. You created a new low-rank logger Temp
3. You want it to accept logs with only ERROR level and above.
4. You created another StreamHandler. Which output to stdout by default.
5. You want it to handle only ERROR level and above
6. Oh, you assigned it to Temp logger, which made 5. redundant since the level is set in 3.
   Oh wait, thought you just want the root logger to do the job since 1.!
7. You logged an ERROR with your logger.

Your Temp logger accepted a string boo at ERROR level. Then told its handler to process the string. Since this handler didn't have any formatter assigned to it, it outputted the string as-is to stdout: boo
After that, Temp logger passed the string boo to his superior, the root logger.

The root logger accepted the log since the log level is ERROR > WARNING. The root logger then told its handler to process the string boo. This handler apply the format string to boo. Add timestamp, add location, add the name of logger that passed the log, etc.
Finally it outputted the result to stderr: 2021-04-26 18:54:24,329::1:ERROR:Temp:boo

Since your code does exactly what you tell it to do, you have to tell it as much detail as possible.

• Only use basicConfig when you are lazy. By removing basicConfig line, your problem solved.
• Use logger = logging.getLogger('__name__') so that the logger has the name of the module. Looking at the log and know exactly which import path that it came from.
• Decide if a logger should keep the log for it own or pass it up the chain with propagate property. In your case, logger.propagate = False also solves the problem.
• Use a dictConfig file so you don't get messed with the config code.
• In practice, you should not add handlers to your logger, and just let the logger pass the log all the way to the root and let the root do the actual logging. Why?
  • Someone else uses your code as a module, can control the logging. For example, not output to stdout but to tcp/udp, output with a different format, etc.
  • You can turn off the logging from a specific logger entirely, by propagating=False.
  • You know exactly all the handlers and formatters in the code if you only added them to the root logger. You have a centralized control over the logging.

make sure your database connection code is in your server.js and not an external file if its in an external file make sure you call it in the server.js or it will not connect to the database

Considering your output:

Restricting packages listed in "symfony/symfony" to "5.0.*"

You currently have something like this in your composer.json:

As per the documentation

When using history mode, the URL will look "normal," e.g. http://oursite.com/user/id. Beautiful!

Here comes a problem, though: Since our app is a single page client side app, without a proper server configuration, the users will get a 404 error if they access http://oursite.com/user/id directly in their browser. Now that's ugly.

Not to worry: To fix the issue, all you need to do is add a simple catch-all fallback route to your server. If the URL doesn't match any static assets, it should serve the same index.html page that your app lives in. Beautiful, again!

To fix this

For Node.js/Express, consider using connect-history-api-fallback middleware.

Follow the documentation

To install the plugin

You can for now use the dev version

Travis CI keeps a cache of your vendor folder in order to make builds run quicker (and reduce unnecessary traffic for them). If you've made some changes to your composer.lock file Travis CI may need to update the files stored in the vendor folder.

Other times it won't need to do this, and so will have a shorter build time.

your problem is here :