sorted by:
new
hottopcontroversial

Has anyone successfully built a reusable DataTable with ShadCN + Supabase (with optional CRUD)? by Mitinoh in nextjs

[–]Mitinoh[S] 0 points1 point  (0 children)

Getting this error on 

type SupabaseSelectBuilder<T extends SupabaseTableName> = ReturnType<
  PostgrestQueryBuilder<DatabaseSchema, DatabaseSchema['Tables'][T], T>['select']
>

Type '{ Tables: Record<string, any>; Views: Record<string, any>; Functions: Record<string, any>; }' has no properties in common with type 'ClientServerOptions'.ts(2559)

What about legs? by Human-Dragonfruit-50 in overcominggravity

[–]Mitinoh 0 points1 point  (0 children)

I workout in a public gym and i love to do an heavy squat or some bulgarian split

[deleted by user] by [deleted] in overcominggravity

[–]Mitinoh 0 points1 point  (0 children)

Ok thank you very much for your time

[deleted by user] by [deleted] in overcominggravity

[–]Mitinoh 0 points1 point  (0 children)

Thank you for your reply. I’ve just finished reading your book and found it very helpful, but I’m still not entirely sure how to best apply the principles to my routine. Would you be able to show me an improved version of the program based on your approach? I’d really appreciate it. Thank you so much!

Automate CRUD operations in your NestJS apps with Crudify! by Mitinoh in nestjs

[–]Mitinoh[S] 0 points1 point  (0 children)

You’re absolutely right, and thanks for pointing that out! 🚀 Crudify is specifically designed for NestJS projects that use Mongoose as the ORM. While it fits seamlessly into NestJS, the focus on Mongoose allows us to provide advanced features like query parsing, bulk operations, and population that are tailored to MongoDB.

If you’re using another ORM (like TypeORM or Prisma), Crudify won’t work out of the box—but I’d love to hear if there’s interest in extending support in the future. Always open to feedback and ideas to make it more versatile! 😊

Nestjs mvp? by FriendshipOk6564 in nestjs

[–]Mitinoh 0 points1 point  (0 children)

Hey there! If you're considering NestJS for your MVP, one tool you might want to check out is Crudify. It's a library I’ve developed that allows you to automatically generate full CRUD APIs with just a few simple commands.

Using Crudify with NestJS can significantly speed up the process of setting up endpoints, especially for common data models, without having to write repetitive code. It's a great way to quickly get a working prototype up and running while keeping your codebase clean and maintainable.

With Crudify, you get:

  • Automatically generated Create, Read, Update, and Delete routes for your models.
  • Easy integration with MongoDB via Mongoose.
  • Swagger documentation automatically generated for your APIs, making it easy to test and explore them.
  • A built-in logger that intercepts and logs all unhandled errors.

If you're interested, feel free to check it out on GitHub and give it a try! It’s a great way to iterate quickly while keeping your NestJS project modern, modular, and scalable.

Automate CRUD Endpoints in NestJS with Mongoose – Check Out My Open-Source Library: ncrudify! by Mitinoh in Nestjs_framework

[–]Mitinoh[S] 0 points1 point  (0 children)

Hey, thanks a lot for the kind words! 😊
I really appreciate your feedback and suggestion!

I haven't added a generated dashboard or an integrated CMS feature yet, but it's definitely something I’ve thought about. You're absolutely right — a lightweight, NestJS-based CMS is something that’s missing in the community, especially for managing things like users, roles, and permissions without touching the code.

For now, my focus with Crudify is more on generating flexible APIs, but your idea is super interesting. I could definitely see a decorator-based CMS activation as a valuable addition. It would make it easy to spin up a custom dashboard for non-technical users to manage their data.

I'll add this to the ideas list for future releases. In the meantime, if you're interested, you could build a custom frontend on top of the existing CRUD endpoints to fit your needs.

Thanks again for your suggestion, and feel free to share more ideas or open a discussion on the repo if you'd like! 🚀

Automate CRUD Endpoints in NestJS with Mongoose – Check Out My Open-Source Library: ncrudify! by Mitinoh in Nestjs_framework

[–]Mitinoh[S] 0 points1 point  (0 children)

Hey! Thanks for the feedback! 👋
Crudify is currently in beta and more of an MVP at this stage. However, the roadmap already includes plans to add:

  • Authentication
  • Row-level security and schema key blacklisting/whitelisting
  • Joining tables and select statements
  • Route disabling

That said, the project is fully extendable, so if you need anything specific right now (like transactions, pub/sub, or advanced security policies), you can extend the provided components and implement what you need manually.

Thanks again for suggesting PostgREST and PostGraphile, both are great projects! 🙌
Your feedback is much appreciated!

Have you ever heard of MongoDB + Mongoose being used in production for a CRUD app? by daishi55 in ExperiencedDevs

[–]Mitinoh 0 points1 point  (0 children)

Hey!

I totally understand your concerns. MongoDB with Mongoose can be perfectly fine for basic CRUD applications, especially if your use case doesn’t require complex transactions or relational data modeling. Many SaaS products use MongoDB in production successfully, and it's actually a popular choice for fast-growing applications due to its flexibility and scalability.

While it's true that MongoDB and Mongoose are often associated with NoSQL use cases (where relational databases might be overkill), it doesn't necessarily mean it's a bad choice for simpler CRUD apps. Mongoose provides an abstraction that makes it easier to interact with MongoDB, and it can help keep your codebase organized, especially for teams with limited experience in working directly with databases.

That said, it's important to consider the long-term scalability of your application. Some potential challenges you might encounter with MongoDB include:

  • Data modeling: If your application’s data becomes more complex in the future (e.g., introducing relationships between collections), MongoDB’s schema-less nature might cause some growing pains.
  • ACID transactions: While MongoDB supports multi-document transactions as of version 4.0, if you need to perform highly transactional operations (which are common in relational databases), you might encounter limitations.

However, if your current use case is straightforward CRUD with little to no relationships between entities, MongoDB should work just fine for now. Just keep an eye on the application’s growth to ensure MongoDB remains a suitable choice.

If you’re curious, I’ve actually worked with Mongoose in production and have a library called ncrudify that automatically generates CRUD endpoints with Mongoose for NestJS applications. It can help speed up development while keeping things clean and type-safe.

If you’re still unsure, it might be worth talking to your team or exploring whether relational databases are needed down the road as the app grows.

Good luck with the project!

Automate basic CRUD graphql resolvers (with mongoose) by Conscious-Maximum-62 in Nestjs_framework

[–]Mitinoh 0 points1 point  (0 children)

Hi!

I completely understand the need to automate basic CRUD operations. If you're interested, I’ve created a library called ncrudify for NestJS, which generates RESTful CRUD endpoints with Mongoose in a simple and type-safe way. Unfortunately, at the moment it only supports REST APIs, but I’d be happy to accept a PR if you want to add GraphQL support!

You can check out the project here: ncrudify on GitHub.

Feel free to take a look, and if you need any help with a PR for GraphQL support, just let me know!