Skip to content

Please Don't Neglect Prisma; Request Jstack Not to Force Drizzle-ORM Binding #51

Description

@luz33c

I'm a big fan of your work and appreciate the effort you put into jstack. I'm writing to suggest some improvements regarding ORM integration.

While Drizzle-ORM is a solid performer and might offer advantages in certain areas, forcing its use within Jstack is limiting. Many developers rely on Prisma, TypeORM, or other ORMs in their projects. A mandatory Drizzle-ORM integration creates friction for these users.

I propose the following:

  • Decouple: Remove the hard dependency on Drizzle-ORM.

  • Examples: Showcase Drizzle-ORM integration as one example within the official documentation and example repository. Crucially, add examples demonstrating integration with other popular ORMs like Prisma and TypeORM. This would provide a more realistic and inclusive view of how Jstack can be used.

  • Optional: Allow users to configure their preferred ORM. This could be achieved through configuration files or environment variables.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions