reflect-metadata | Prototype for a Metadata Reflection API for ECMAScript

The @nestjs/cli dev dependency should be up on version 8 with the rest of the @nestjs/ dependencies. @nestjs/cli v5 doesn't have a start command

I fixed it by removing the third party plugin and setting it like this

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:

For my version of this error, the issue seemed to be that I was importing a file with an alias in webpack from within the same directory.

To give an example, I had this directory setup:

There are several reasons why the body tag of your angular app fails to render on the server side. Here's a checklist:

• First make sure your live environment supports NodeJS. Without NodeJS on the server, you can't use server-side rendering
• In Visual Studio, try changing your ASPNETCORE_ENVIRONMENT environment variable from DEVELOPMENT to PRODUCTION and run your application. In some cases the app behaves differently in either configuration (looks for the main.js file in another location when PRODUCTION). After starting the debugger and trying to prerender a view, you may see some exceptions in the Visual Studio Output window.
  • In my case the main.js file had to end up at ClientApp/dist/main.js. So I had to modify angular.json changing the projects:ClientApp:architect:build:options:outputPath to dist (see also)
• If you experience this problem using Visual Studio, do always look at the Output window for errors which will point you in the right direction.
• If you're hosting a PWA (for example through @angular/pwa), then it's totally normal that you're getting an empty page when going to View source in the browser. If you'd then ctrl + F5, you'll be bypassing the angular service worker which shows you the prerendered html source. This is something you shouldn't bother about. Google, Bing, ... will actually fetch and index the server-side rendered version of your page.
• If you're using ASP.NET Core 3.1 or earlier, you cannot have an async lambda for your SupplyData delegate. SupplyData is not a Func and is not being awaited in the source code of ASP.NET Core. I changed this in my port to .NET 6

The main issue here is that Sanitize() gets called once per decorated class property declaration, and so for any given class property there will be only one currentValue. Meaning that two instances of the class will share the same currentValue. If you want to store one value per decorated class property per class instance, then you need access to class instances, and you will have to store the value either in those instances (via a property key that isn't going to interfere with any other properties), or in some map whose key is those instances. In the following I will show how to store the value in the class instances, and to avoid worrying about property name collision I will use the symbol output of the Symbol function, which is guaranteed to be unique.

Also note that Sanitize() is passed the class prototype as the target argument, so any manipulation you perform on target will affect the prototype and not any instance of the class. When you write target[propertyKey], you are looking up the property in the class prototype, and string-valued properties will almost certainly not be set in the prototype. So this is probably not necessary or useful, and we should get rid of it.

So if you only have direct access to the class prototype, how do you do anything with class instances? Well, to do this, you should use the this context of the get method and set method of the accessor property descriptor you pass to defineProperty(). And that means get and set need to be methods or at least function expressions, and not arrow function expressions which have no distinct this context.

Okay, enough explanation, here's the code:

Try add this to your webpack config:

When the App is rendered in Jest it cannot find the 'root' element so one solution I have found is to provide a div element when the 'root' doesn't exist.

From what I've found online, this seems like a common issue to projects using Jest and upgrading to Angular 13. Our project doesn't use nx but are the updates to our Jest config: