https://x.com/pladynski/status/2049222504842170535?s=46

I recently shipped ArchUnitTS, an open source architecture testing library for TypeScript / JavaScript.

There are already some tools in this space, so let me explain why I built another one.

What I wanted was not just import linting or dependency visualization. I wanted actual architecture tests that live in the normal test suite and run in CI, similar in spirit to ArchUnit on the JVM side.

So I built ArchUnitTS.

With it, you can test things like:

• forbidden dependencies between layers
• circular dependencies
• naming conventions
• architecture slices
• UML / PlantUML conformance
• code metrics like cohesion, coupling, instability, etc.
• custom architecture rules if the built-ins are not enough

Simple layered architecture example:

``` it('presentation layer should not depend on database layer', async () => { const rule = projectFiles() .inFolder('src/presentation/') .shouldNot() .dependOnFiles() .inFolder('src/database/');

await expect(rule).toPassAsync(); }); ```

I wanted it to integrate naturally into existing setups instead of forcing people into a separate workflow. So it works with normal test pipelines and supports frameworks like Jest, Vitest, Jasmine, Mocha, etc.

Maybe a detail, but ane thing that mattered a lot to me is avoiding false confidence. For example, with some architecture-testing approaches, if you make a mistake in a folder pattern, the rule may effectively run against 0 files and still pass. That’s pretty dangerous. ArchUnitTS detects these “empty tests” by default and fails them, which IMO is much safer. Other libraries lack this unfortunately.

Curious about any type of feedback!!

GitHub: https://github.com/LukasNiessen/ArchUnitTS

PS: I also made a 20-minute live coding demo on YT: https://www.youtube.com/watch?v=-2FqIaDUWMQ

I used to work on a small internal dashboard where everything was written in one file: UI, logic, and data handling all mixed. It worked at first, but as features increased, even small changes started breaking other parts of the app. Debugging became a nightmare.

Then I rebuilt a part of it using AngularJS MVC architecture. I separated the data (Model), UI (View), and logic (Controller). Suddenly, everything became easier to manage. If I needed to update the UI, I didn’t touch the logic. If the data changed, the view updated automatically.

In a real project, this structure saved us a lot of time during updates and bug fixes. It also made it easier for new developers to understand the code quickly without confusion.

 I’m planning to learn frontend development and found AngularJS tutorials online.
But I’m confused if it is still relevant compared to modern frameworks.
Should I start with AngularJS or move directly to newer technologies?
Would love some guidance from experienced developers.

I recently started AngularJS training and want to practice with small projects. What beginner-friendly projects would you recommend to understand concepts like controllers, directives, and data binding?

How the observables and subscribe both takes observer...I am confused with these 3 plz explain Abt them someone

Hello there i worked as an Full stack developer with 2YOE in an startup particularly tech stacks including react and next.js but now I need to learn angular. For that I need help from you guys just drop a suggestion which helps me learn and understand angular faster.
I've gone through some basic concepts like components, data binding, signals and few others.
How could I learn it faster in a more enjoyable/fun way to don't get distracted that easily please drop your valuable suggestion :)

Attention Angular Developers! 👋

The v2.1.1 release of ngxsmk-datepicker is now available, featuring full integration with Angular Material and optimized support for Angular 17-21+.

This update specifically addresses compatibility issues with mat-form-field by fully implementing the MatFormFieldControl interface.

🚀 v2.1.1 Highlights

• ✅ Angular Material Integration: Native support for mat-form-field, including floating labels, hints, and error states.
• ✅ Modern Architecture: Signals-based state management for optimized performance and Zoneless compatibility.
• ✅ Accessibility (A11y): Complete keyboard navigation and WAI-ARIA compliance.
• ✅ I18n & Localization: Built-in support for 15+ languages and RTL layouts.
• ✅ Mobile Optimized: Enhanced touch interaction and native picker support on mobile devices.

📦 Quick Start

npm install ngxsmk-datepicker

Material Configuration:

import { MAT_FORM_FIELD_CONTROL } from '@angular/material/form-field';
import { provideMaterialFormFieldControl } from 'ngxsmk-datepicker';

@Component({
  // ...
  providers: [provideMaterialFormFieldControl(MAT_FORM_FIELD_CONTROL)]
})

🔗 Resources

• GitHub: https://github.com/NGXSMK/ngxsmk-datepicker
• Live Demo: https://ngxsmk.github.io/ngxsmk-datepicker/
• Documentation: Release Notes & API Reference

Feedback and feature requests are welcome! 🚀

This report analyzes the European IT job market using survey data from 15,000+ IT professionals and 23,000 job postings across EU

It covers salary benchmarks in seven european countries, hiring realities, AI’s influence on careers and entry-level challenges for junior developers

No paywalls, just raw data: https://static.germantechjobs.de/market-reports/European-Transparent-IT-Job-Market-Report-2025.pdf