swagger-ui-express | Adds middleware to your express app | REST library

It looks like you have a service named database_ignite in your docker-compose.yml file. Docker by default creates a host using the name of your service. Try changing your host from database inside your index.ts file to database_ignite:

app created by express() doesn't have a close method. But const server = http.createServer(app);, the server has a close method.

You can start the server and listen to the connections in beforeAll and call server.close in afterAll. To achieve this, you need to export server so that the test file can get the server.

The statement inside the if (require.main === module) block will only be executed when running this script by node server.js.

E.g.

app.ts

I am not sure in your implementation, but as per openapi and my implementation this is working for me,

You can add authorization in definition > components in securitySchemes,

This is a known issue with Jest. See https://github.com/facebook/jest/issues/9771 and https://github.com/firebase/firebase-admin-node/issues/1465. You can find some workarounds in the above issues.

The solution that worked for me was delete package-lock.json and run: npm install @babel/node -g. :)

This kind of error is usually when you need to add the @types dependency for the module.

I found the solution and it may help someone else. To run dotenv command in terminal we need dotenv-cli. Installing dotenv-cli with yarn add dotenv-cli solved my problem.

Since the message appears in the console(see comments):

Refused to connect to 'localhost:3005/auth/login' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.

this means that CSP is interfering and blocks connects. The fact is that 'self' covers standart ports only (80 for http:/ws: and 443 if https:/wss:).
Therefore you have to change default-src 'self'" to the default-src 'self' localhost:3005 (with exact port number) in the Content Security Policy. Since connect-src is omitted, it fallback to the default-src.

May be better to use default-src 'self' localhost:* rule (* means any port number). Browsers treat localhost as safe source (you own device) so is secure enough to allow any ports on localhost.
In this case, fallback directives (img-src, script-src, style-src, frame-src, etc) will not block any sources downloaded from localhost on any port, what can be convenient in development mode.

Note 1: however, if you need to prepare CSP for the production mode, you can place blocked sources in the relevant directives. In this case CSP will be default-src 'self'; connect-src localhost:*; because blocking is observed in the connect-src.

Note 2: Quite possible CSP header default-src 'self' is set by Helmet middleware the latest version of which self-publishes CSP with a default rules.

It looks like you're attempting to run the migrate command on your host OS, which does not know about a host called postgres.

You will need to run the migrate command within the app container (which is in the virtual network that has a host called postgres):