documentation VS ts-brand

Have you heard about Feature-Sliced Design? I have personally found it extremely helpful as the project grows larger, though it can have a bit of a learning curve

In our case, the current folder structure resembles Feature-Sliced Design:

Feature-slice design is the one and only correct solution imho

(https://feature-sliced.design/)

for large spa I recommend https://feature-sliced.design/

There are many more benefits of using feature sliced design which are well documented in the docs. I highly recommend you to check it out and learn new ways of organizing your frontend project.

Hi, I use feature-sliced design for big or middle spa. Excellent solution for scalability! https://feature-sliced.design/

Ссылка на офф сайт.

You can also see a way around this restriction in "DDD, Hexagonal, Onion, Clean, CQRS, ... How I put it all together" and Feature Sliced.

The closest way to get nominal typing in TypeScript is with type branding. I haven’t actually used this small library, but it illustrates the idea: https://github.com/kourge/ts-brand

For this reason I've actually started to enjoy the idea of branded types. Instead of passing around entity IDs as numbers you can have the compiler ensure that you get a specific kind of number, or at least have to explicitly cast to get around this limitation.

There is a way to make TypeScript understand that we want a particular type—use branding, branded types. Branding enables to keep track of exactly how types are used, but makes the code a little more complicated.