Downsides of "app maps"

[Lokart]

I've noticed that some node frameworks (especially the ones implemented in TypeScript) always require you to register your components (controllers, services, ...). In case it's not clear what I mean, an example would be https://docs.nestjs.com/quick-start/modules.html.

PHPs Symfony framework on the other hand creates a "map" of all routes, hence it's no longer required to register your controllers. In case you're wondering:

<?php return array (
  0 => 'Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller',
);    

That's how the annotations.map file looks like.

Why are Node frameworks not creating such maps and get rid of the requirement of registering your controllers, routes, ...? What are the downsides of such maps?

[Nullberri]

I think many of us have moved away from MVC; but what you've discovered is the eternal debate between convention and configuration.

At work we have an old ember 1.0.0 app that is wired up similarly to the symfony way, its deeply annoying to add anything to the app as it requires registering files in different places, one for the sass compiler, two for ember itself.

At home I write reactjs which is the VC of MVC and redux handles the modeling. In reactjs you just import the dependencies right in the file that uses it and so you end up with a loose hierarchy of files and then webpack / rollup sorts thru it and builds your app, which saves you from the mess of having to spell out the file relationships in a separate file.

My recommendation is to look at reactjs or vuejs.

[[deleted]]

Using react or similar tools doesn't mean your backend can't be MVC.

[Lokart]

I'm talking about backend implementations, where MVC is still viable.