tsconfig-paths | Load node modules according to tsconfig paths | Runtime Evironment library

This app worked for a long time in docker container and recently it even doesn't launch.

In docker container I've this error:

the goal is to use Cypress for component testing and e2e testing mainly. Install and configure all Cypress correctly, configure Cypress in the 'cypress open' script to open E2E related tests and configure the 'cypress open-ct' script for component tests, all settings work very well.

The project is already ready and I have absolute folders configuration, when I import a component from '~/components' I am accessing 'src/components', I am not able to make the proper settings to be able to access the absolute folders because when I run the cypress open script -ct doesn't seem to run 'file:preprocessor', where you need to run it to run the webpack where you have the absolute folder settings. I tried several alternatives and this was the one that worked the best because when I run the 'cypress open' script cypress executes 'file:preprocessor' it applies the webpack settings and if I try to import a component using '~/component/InputDate' it works , however 'cypress open' is for E2E tests, I can't run unit tests through this script.
I can be wrong about the cypress open script not running component tests correctly but I'm looking for a solution to the big problem that is these absolute folders.

I tried the tsconfig.json files configuration solution but I couldn't make it work because I use it in the jsconfig.json project, I tried to use tsconfig.json I used the 'tsconfig-paths' package and got no result.

For this project, I have a monorepo with 2 workspaces (api and frontEnd). I have upgraded node from V10 to V16 recently and the migration is almost complete. I can run it locally, but building is not possible anymore.

When I run yarn workspace api start:dev, defined in api/package.json as "start:dev": "cross-env NODE_ENV=development npx ts-node-dev -r dotenv/config -r tsconfig-paths/register --respawn --transpile-only src/index.ts", it runs smoothly on localhost.

When I run yarn workspace api build:ts, defined in api/package.json as yarn run tsc, I get errors of the following type (I kept only 1 error per file to respect the question character limit, but there are over 2000 lines):

We are using typescript and exporting one class as following (we are using nuxt and class style component if this relates to webpack issue).

I struggle to use JEST for some cases where running the tests I get

Test suite failed to run

Am getting an error when I am deploying serverless lambda function on AWS

After upgrading react-scripts to v5, craco start does not work properly. App starts with no error but in browser, there is a blank page and if i open inspector, i only see index.html codes not react codes. It was working well with react-scripts@4.0.3. Here is my local files;

package.json

It's 3 days i am on this problem of E2E tests on my GraphQL application with NestJS + Apollo / Express.

When I am running my app with serverless offline or directly with my main file, it's working perfectly. I have my graph and all things I need :)

But, when I am running E2E tests with Jest, I received an error from the await app.init() inside the beforeEach.

After playing with the package.json and dependencies, the error throwed is TypeError: (0 , schema_1.makeExecutableSchema) is not a function.

Someone have any idea please ? I am totally blocked ... :(

The AWS compilation errors from within node_modules are occurring the build