Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Every way is opinionated of course, node best practices suggests "structuring by components", in this way I would have src/features/user to contain all related to user code (features is more common), and inside of user I'd have auth, inside of auth I'd have all related to auth code. Nesting of folders is really a savior when you have like 100 features, not necessary on small projects, but I nest folders when it makes sense from beginning
For example Nest.js: https://github.com/CatsMiaow/node-nestjs-structure/tree/master/src, there is auth with passport.js. (I don't suggest Nest.js and don't use it myself, sharing only structure, file naming)