How to see karma output in debug window?

[antonpegov]

Now tests results are showing only in terminal.
But browser window is always empty

[qdouble]

I've been very busy with my own projects, but my setup is totally different now. Once I have everything set in a way where it will be easy for everyone to use, I will make a major, breaking update to this repo.

[vlados]

@qdouble When we can expect this breaking change?

[qdouble]

@vlados I'll try to see if I can spare a couple of hours this week to pull out some of my current project.

I'm currently putting a lot of work and study towards leaving Angular and frameworks in general behind. I'm going to stick to minimalistic/functional libraries and just deal with plain TS/RXJS.

1. Angular abstracts you far away from how your app really works, so it can make debugging a huge pain and also forces you to having to do everything the "Angular way"
2. I really need to have tighter integrations between the backend/frontend. Keeping everything in sync when your project is disjointed becomes a pain and you also end up having a ton of boiler plate and repetitive code.

I'll still have to maintain to my existing apps though. I'm moving into a more monorepo style, so I'll have to see what's appropriate to put into a starter build.

[vlados]

Is there any way I can help?
Also for tighter integrations we are using swagger-codegen so the client is using a autogenerated lib from the backend code. This make it easier when someone make a mistake and alot easier to test the backend and frontend

[qdouble]

@vlados as long as nothing critical comes up, I'll work on the update tomorrow and then once there's that starting point, you can help me perfect it from there if you want to. I'm using Lerna and Yarn for the multirepo setup. You still have to build angular separately though, because of the way it compiles, but with using the new Typescript project references, you can compile all of your own helper libraries you create at the same time. One of the biggest issues I'm looking to solve with this setup is to keeping projects in sync with each other.

Swagger looks interesting, but I I have doubts about it being better than a custom solution. On my new projects, the plan is to have the server and frontend validation essentially use the same code as well as share interfaces and classes. Also, without the angular restrictions, having fully dynamic pages should become easier as well. I was working on an animated countdown clock last weekend with angular, and something as simple as dynamically changing the speed seemed unworkable without hacks.

While I can see the benefit of frameworks when working with large teams or doing stuff for clients, as a person who mostly works on his own projects, I think I'll be better served long term by just forking and customizing a minimalistic view library and router. Then I can just roll out al ofl my own code after that and not deal with opinionated framework restrictions, bloat or clunkiness.

I'll still have to maintain my angular projects for years and update them, so I'd definitely stay tuned into it as well and I won't mind maintaining the starter if I find it useful, but I guess it has to move beyond just a basic setup and be something I'd actually use in production.

[qdouble]

Going through it, I'll have to put it off for a little while. As the setup is more advanced than the current starter, I'd really have to go through all of it and make sure it'd work for general usage and be easy enough to understand. I still have a work project I need to knock out before I can dedicate a lot of time to that.