npm-run | Run locally-installed node module executables | Runtime Evironment library

After many hours of intense programming ... I finally found the problem.

Be careful if you use some "alias" for imports, because it can overwrite some of the packages used.

Here, i use the @graphql alias, and it breaks all my tests. When I remove it, the problem disappear.

My colleague solved it by moving to Vite. My suggestion would be to drop webpack and use Vite instead.

Migration guide for Vue 2 to 3 here: https://v3-migration.vuejs.org/ Vuetify migration guide: https://next.vuetifyjs.com/en/getting-started/upgrade-guide

The errors you've shown are coming from the ngUniversal/common dependency, as you can see by the error messages. The dependency is set to next in your package.json. Try some specific version numbers until you get one that works. Do the same for any other packages with the same message. Versions can be found here: https://www.npmjs.com/package/@nguniversal/common

The first number is the major version, when that changes it indicates a breaking change.

According to this page https://docs.nestjs.com/graphql/unions-and-enums

enums need to be declared with the function registerEnumType

Unfortunately, what you're trying to do isn't possible. From the Node documentation:

Node.js will treat the following as ES modules when passed to node as the initial input, or when referenced by import statements within ES module code:

• Files ending in .mjs.

• Files ending in .js when the nearest parent package.json file contains a top-level "type" field with a value of "module".

• Strings passed in as an argument to --eval, or piped to node via STDIN, with the flag --input-type=module.

If possible, you should just copy over the package.json in your Dockerfile - that's what Node expects.

Otherwise, if you absolutely can't have a package.json in your Docker image, then node --input-type module --require dotenv/config < main.js should do the trick.

Is it possible that my code is deprecated?

I'm afraid it is.

Here is one of the major changes of v6.0.0-alpha.4:

Removed the API. We don't support navigation on the initial render in v6, so this API is unnecessary.

I ended up storing the status code and the redirect URL in the Redux store and checking them on the render server after rendering.

For the status code I dispatch the setStatus(404) action in the loadData function of the NotFound page component.

And this is my solution for the redirect URL:

In whatever start script you are trying to run, you need to include nodemon

ex:

Update

It's likely a bug introduced in CRA5: issue

Using WDS_SOCKET_PORT=0 will allow the solution to work with all debug configurations.

=================================================

I notice that, after upgrading to CRA5, the react dev client starts to respect the current page's protocol. That is, if you are debugging your asp.net core project using https locally, the react dev client will also try to connect to node dev server with wss(websocket over TLS) which is not enabled by default. There are several ways to get around with this, the simplest way would be:

1. create a file with name .env.development in the same folder where lies your package.json.
2. put WDS_SOCKET_PORT= in .env.development you just created. should be 5001 by default if you are using the SPA template generated by dotnet cli.

This will allow the ws connection initiated by react dev client to be proxified to node dev server with UseReactDevelopmentServer middleware.

Resolved this finally with help from netlify team (see here)!

Best advice:

To debug I’d suggest starting again from a fresh clone of your own repo and paying attention to the steps you need to perform to get it working locally. You’ll need to ensure that the instructions you provide Netlify perform those same steps.

This worked for me locally