yassineldeeb / create-prisma-generator Goto Github PK

View Code? Open in Web Editor NEW

179.0 1.0 7.0 3.3 MB

Get started developing your own ◭ Prisma generator by running a single command.

License: MIT License

TypeScript 84.29% JavaScript 15.23% Shell 0.47%

prisma prisma2 prisma-generator cpg create-prisma-generator boilerplate cli dev-community typescript generator

create-prisma-generator's Introduction

Usage • Blog • Architecture

⚠️ Note

create-prisma-generator doesn't support Prisma 4 yet, it works with Prisma 3, but that doesn't mean that you can't upgrade on your own quite smoothly.

Any contributions to support Prisma 4 in the create-prisma-generator are highly appreciated and will be part of the authors/contributors section of this tool.

Prisma

Prisma is Database ORM Library for Node.js, Typescript.

Prisma has a concept called "Generator". A generator is an executable program, which takes the parsed Prisma schema as an input and has full freedom to output anything.

The most prominent generator is called prisma-client-js. It's the ORM Client powering the main TypeScript and JavaScript usage of Prisma from Node.js.

Generators will always be called when you run prisma generate. However, only the generators mentioned in the schema.prisma file are being run.

Strongly recommend reading the full article, It's pretty damn good

Motivation

As a community, developing prisma generators is really hard cause that's a very new concept to us so It's like knowing JS but being exposed to do ML with it for the first time and there is nothing documented about @prisma/sdk (this is done intentionally) which has a very great utilities when developing or testing prisma generators and the only way you can get started is by looking at other generators code which might be useful to get you started.

I'm really obsessed with this architecture that Prisma Client is built on and I can see a bright future for Prisma Generators from the community to integrate Prisma nicely with different frameworks or make tools that can beneift from Prisma models.

But unfortunately I didn't have a smooth experience developing my prisma generator.

So I created this CLI to encourage developers to make their own prisma generators to have a smooth experience with all of the annoying repetitive things carried away like: getting started boilerplate, publishing, testing the gen locally by running prisma generate, ..etc

Also Created a blog on dev.to where we're gonna be discussing the hello world prisma generator together that this CLI has setup for you and the different concepts you'll come across when developing prisma generators, Check It out here

Usage

Answer the prompt questions to setup your project, The project setup will be based on your answers.

npx create-prisma-generator

What’s Included?

Your environment will have everything you need to build your prisma generator like an elite open-source maintainer:

Hello World Prisma Generator.
Typescript Support.
JavaScript setup with babel to enable the usage of the latest JS features.
Automatic publishing workflow with Github Actions.
Workspace setup for testing the generator locally using prisma generate.
Scripts for development, building, packaging and testing.
Support for most package-managers yarn, pnpm and npm.
Automatic semantic release with safety in mind using commitlint & husky to validate your commit messages.
Test environment using Jest with an example & fixtures to help you get started.
Dependabot for keeping dependencies up to date.

Architecture

Read Architecture.md to understand how everything is working.

Prisma SDK reference

Read Prisma_SDK_Reference.md

Community

The Create Prisma Generator community can be found on GitHub Discussions, where you can ask questions, suggest ideas, and share your projects.

Contributing

We'll be very thankful for all your contributions, whether it's for helping us find issues in our code, highlighting features that're missing, writing tests for uncovered cases, or contributing to the codebase.

Read the Contributing guide to get started.

💚 All Thanks to Prisma's brilliant developers for making such an awesome Node.js ORM that can be easily built on top of it.

create-prisma-generator's People

Contributors

Stargazers

Watchers

Forkers

dngferreira robertonegro linecode niranjithcu jedwards1211 2wce mubaidr

create-prisma-generator's Issues

Feature Request: Support Travis CI

Is your feature request related to a problem? Please describe.

Github Actions is the only supported CI workflow.

Describe the solution you'd like

Supporting Travis CI by providing the boilerplate configurations to automatically publish the Prisma generator to npm.

`types` directory empty after running `npx prisma generate` in the usage project

Bug description

Fresh "create" with no changes does not output any files to the types directory. The directory is created, but no files within after a generate.

To Reproduce

Screenshot for prompt questions answers:

run the "create" flow on macOS then:

❯ cd packages/usage
❯ git log
commit ed3d8e4e830f8ed413604af4a3c710e09d329929 (HEAD -> main)
Author: Adam Mork <[email protected]>
Date:   Sat May 13 19:42:43 2023 -0600

    feat: added husky for safety commit-msg

commit 4b005bd347a2bc22bf86a65c3484c1e01a31a968
Author: Adam Mork <[email protected]>
Date:   Sat May 13 19:42:42 2023 -0600

    init
❯ pwd
/Users/adam/Projects/pntmnt/prisma-generator-types-test/packages/usage
❯ npx prisma generate
Prisma schema loaded from prisma/schema.prisma
prisma:info prisma-generator-types-test:Registered

✔ Generated prisma-generator-types-test (1.0.0) to ./types in 4ms

┌─────────────────────────────────────────────────────────┐
│  Update available 3.12.0 -> 4.14.0                      │
│                                                         │
│  This is a major update - please follow the guide at    │
│  https://pris.ly/d/major-version-upgrade                │
│                                                         │
│  Run the following to update                            │
│    npm i --save-dev prisma@latest                       │
│    npm i @prisma/client@latest                          │
└─────────────────────────────────────────────────────────┘
❯ gs
# On branch: main  |  No changes (working directory clean)

Expected behavior

files in the types directory

Environment & setup

OS: macos ventura 13.0
Node.js version:

❯ npx --version
9.5.0

--skip-check CLI failure

Bug description

I have trouble trying to pass the --skip-check argument on CLI

Passing --skip-check it's still throwing the message

> npx create-prisma-generator --skip-check

? what's your generator name <package name without convention>

Prisma recommends you to use this naming convention:
 prisma-generator-<custom-name>
use the `--skip-check` flag to skip prisma's recommendation.

Environment & setup

The installation process was executed as described on README.

OS: OS Name Microsoft Windows 10 Pro 10.0.19045 Build 19045
Node.js version: v16.18.1

logger.error just print nothing in console

Bug description

A clear and concise description of what the bug is.

To Reproduce

Screenshot for prompt questions answers:

If applicable, add screenshot for your terminal showing the answers for prompt questions.

Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help better explain your problem.

Environment & setup

OS:
Node.js version:

Bug 🐛: github actions fails when using npm

Bug description

When creating a new Generator, the GitHub Action Pipeline does not work

Bug: npx create-prisma-generator doesn't work as intended

(note): Using PopOS 21.0 with node 16.13.1 and npm 7.5.4

Running the npx create-prisma-generator command spits out

# ....
t̎ͧè̑s̆͂t͒̉́iͯ͊͗n͗͌̎gͣͫ ̎͐tͪ̆ ҉̧̮eͪ̉s͛͛ ҉͚̝̼ẗ͑iͭ͊n̽ͯg̈ͥ ̾̾t̆͑ ҉̵̵͖e̒̅s̊̎t̄̑ͯͧiͤ̒n͆ͪg͑̓ ̂ͩt̿ͩeͪ̓sͤ̋t͌͛ͮi̅ͭnͫ͆̽ ҉̴̯͔͡g͂̎ ̂̎̈ ҉̴̷tͫͬeͯ̚̚s͒ͤ̿t̓͌i̊̈ͯ́n̿̇ͯg̃̄͑ ͮ̐tͪ̑ȇ̌̉ŝͤ ҉̗̣͝ẗ̌̾ ҉̵̧i̔͆̎ ҉̴̪̟n̈̍̿g̋̋ ̽ͤt̅̇ẻ͊sͩͮt͆͛iͫ͛n͛̚ ҉̡̯̘͞g̋̒
tͣ̽ ҉̣͙͢e͋̇s̃͆ ҉̱́͢t̽̊i̐ͮn͒ĝ̚ ̇ͬͩt̐ͥeͬ̽s̆͑t̆̽i͆ͤǹ͒g͂̚ ́ͥt͐́é̈s̃̚t͌̓ǐ̉n̈̅ ҉̱̬͖ġ̽ ͨ̾t̎͒e̓ͮs͆̾ṫͫ̔ȉ͒̐nͫ̇g͊́ ̂ͯt̿͌ ҉̸̢e͐ͦs̋͌t̒ͩ̂i̿̆n̽ͬgͨ́ ̊ͪt̏̅e̒̓s̔ͯt̋ͦîͨ ҉̰͔n̿ͫ̽ĝ̈ ͌ͨͤ ҉̹͚͖̗tͧ͑eͮͪs̈̃ ҉̠͘͝tͬ̾i͊̊nͣͦ ҉͕̝g͑ͩ
ẗͫͬ̓e̔̎s̀ ҉́͞t̆̚i͆̏nͥ̊ḡ̏ ̈ͨt͌̉ͩ ҉̡̧e͋̈ ҉̴̡s̉̀t͑̑ĩ̾̂n̄ͮgͦͤ͐̂̈ ҉̨͕ ̈ͭt͋̓̚ ҉̧͝e͊ͨs͑͒t̔̆iͧ̑ṅ̓g̒͒ ͥ̔͒t̓ͩ͊eͦͮs̈̔ ҉̴͝ẗ͐ ҉̯̩̘iͩ̏̂n͑͂ ҉͘͠gͦ̐ ҉̡̭̭ ̔t͛ͪͮeͯ̔̂sͨ̏ṫ́ ҉̣͙̲̞͢iͧͥnͩ̃g͒ ̈̑t̾̚eͭ̈šͬt̑͋̓i̽̒nͦ̑gͭ͛ ͫ͌t̍̀e͑ͩs͌͆t̐ͫi͛n͋̑ͮg̒̽̈
t͒͑eͯ̿sͣ̉ ҉̵̗͉̫tͧͭ͆ỉ̏̚ñ̏g͗ͯ ̈̾t̎͌̾ȅ̃sͤ͋tͪ͑ͩi͗̔nͭ͌g̍ͯ̚ ҉̱̫̘ ͨ̿t͑̀e̔ͨ̆ͣs̆t̑́i͛̃n̉̍̓gͦ̿͊ ̈̑ẗ̔e̔̄s̈̈̏t͐͊ĭ̈ ҉̻̦nͫͫg͋̚ ͮ̌ť̈ê̓s̒͐t̽͌i͒͗nͫ̋̎ ҉̨͈g̏̂ ҉̝͕͞ ͥ̐̿t͒͒eͧ͂ ҉͈̬͜͜s͒͆t͐̓iͪ̈n̄ͫg͐̒ ̉͐t̊̍ ҉̙̯̦̗̕eͦ͌s̍̂ťͭ ҉̳̼iͮͦn̿ͫgͣ̓
t̔̾e͆̏ ҉̴͍s͒̍t̓͂i̐̊ͪnͫͬgͬͤ ̆̎ ҉͕͍̩̟t̃͗eͯs̓ ҉̡̺tͭ̍ȉ̈̾n̈̔g̐̀ ̊ͪ̃̋ ҉́͢͝t̊̐̑e̐͑s̎ͣ͊ẗͣi̿̄ ҉̸̡̺nͭͤgͥ̃ ͬ̔t͌͆e͋͗s̆͒ ҉ ҉̘̀ẗ͆i͊ͯn̊̉gͨ̍ ҉̸̖͉̕ ͤ͊ ҉̡͠t̀ͩe͗ͧsͯ̇ ҉̛̀ ҉̤̞tͤ̓ͦiͪ̄͒n̾͗gͬͤ ͋͐t̍ͦe̓̋s̍̚t͊͑̒iͣ̈̎nͨͭgͯ̋ ҉̼̀ ͗ͩt͒̉́e̐̉s͑̽t̑̚i͑ͪnͩͦgͣͪ͑
tͯͤêͥsͤ̀t̽̈ỉͭn̈͌ͥg̈ͨ ͐ͦ̍tͣ͂e̐͆s̈͋t̏̾̀i͒͂ͦ̉n͗ͮg̏͛̓ ̋͆t̄̈ȇ͑s͛̽tͣͩi̒͆ͭn̉ͦ ҉̞̬̱̘ḡ͆̈ ͦͧṫͪ̚ȅ̚sͣ̓t̓͒̔̈i̐ͮn̐̂̇ġ̌ ͧ̃t̔̅ ҉͎͉e̐͌ś̆́t̄̈ͥi̅̈ͥn͒̈gͨͬ ͥ̈tͨ͂ě̀s̓ͤtͮ̚i͆͆ ҉̛̘̗̤n͂͂ĝ̾ ̐ͮt̔͗ẻ̒s̀͆t͆͊ȉ̔n̐͒ḡ̃
tͧ́e͑͂ ҉ ҉̧̛̬sͪ̒ ҉̨̻t̅̓ī̓n͆̈ͣgͭ̐ ͪ̇tͯ̎ ҉̵̩̜̀ͅe̓̊s͗͛̅t͛͗́i͆ͪnͭͫg̿͆ ̑̋tͮ̚eͧ̇s͂̓t̒ͤi͗̇n̑ͦg̐̌͒ ҉̵̧ ̉͆t̎̓e͒ͪs̍ͮt̀̉ĩ̾̂n̑ͦĝ͗ ͭ͒̈t́ͭ̒ẽ̈ͥ ҉̵̙̪ͅsͯͣt̎͐i̓̄nͤ̒g̅̈̎ ͩͣẗͨë͐s͂ͤ ҉̳̰t̔̅ ҉̰̀î̚n͒̿gͪ̄̓ ́͗ṫ̊e̐̇sͥͦ̀t͗͑ȉͦ ҉̴͡n̆͛g̏ ҉̵̥
tͦ͑ͭe̒̈̈sͬ̋t͂̔í̚n̏ͧǵ͂ ̆͊t̎̓e͛͂ ҉̡͡ ҉͇̰sͥ̈t͑̈i̎̚n͛̍g̍̂ ͨ̍tͭͣ̋e̒͌̆ ҉̣̲sͣ̓̔t̃ͥͥi̽̂n̋́gͬ ̈̅ ҉͍͍͞t́̔͒ẻ̎sͫt͆ͤiͧͭ̅n̂͒g̿̐ ̍ͩ̈tͦ̅ě̃̋ ҉̫̯s͌́tͩ̉ͬiͧ̓̓ ҉̨̥̹n͒̏g͊ͧ ̊͆t̄ͧ̐eͦͪͣs͂̾t͌̿̚ǐ̏n̉͊ǧ̈ ́̓t̄̚e̓͛sͤtͨ̍iͨͧn̏ͥg̈̋
t͒́e̐̊sͭͯͮtͯ̊i̐̓n͆̓͐gͣ̅́ ̈̃tͬ̈͑eͩ̈̎ ҉̴̨͇̪s͂͌t͑ͭi͋ͤñ̐gͫ̅ ҉̵̝ ͣ͐tͨͨeͣͩ ҉̪͜s̓ͤͤt͋̂i̊̄n͑̽g̔͛ ̅̊t́ͤëͤs̈̇ṫ͗i̓͛nͫ͌ͯ̆g̀̓ ̏͐tͯͯe̓̑s̈͂tͭͨì̊n͊̔g̽̓ ҉̧͕ ͤ͛tͨ͌e̐̇̈s̾̍t͆ͦ̈ȋ̑n̏̔g̍̎ ͥ̒t͗̒e͗ͧs͌ͣ̈ẗ̍͑i̎̒͐ ҉̡̥͜n̿͋́ĝ͒
t͂̓ė̈͋ ҉̶͓͙̟̣̫s̓͐t̀̐ ҉̵̮̠ȋ̀͊̇nͦ̃g̑ͣ͐ ҉̬͍́ ̈́t̏̂e̊̽s̒̊t͆ͧi͗ͦn͊̑gͦ̾ ̍ͩ ҉̤͟t͗͌͑̚ ҉̛͔̣e̐̎s͛̊tͧ̍̏ĩ͊ǹ͌ḡ̏ ͫ̈tͦ̎̄e̅̃ ҉͘͝s̀̂̓t̎͐iͬͧn͑́g̾̓ ͒̒t̀̔ͥe̿ͬsͧ̈t͑̃ĭͮn̆̚ ҉̨̲͠gͦ̚ ̓ͩ̋tͨ̂e͊ͤsͣ̈tͭͦ̐ì̐͊n̎͆g͑̾͒ ͥ̈t̐̍e͛̋sͣ͌tͥ̑i̋͒nͫ͛g͗̓
tͤͥeͤ̂͂ṡ̎ͮt͆͛ĭ͒n͗̊g̽̑̂ ̅̅t͛̾e̊̑ ҉̴̠s̒͂͐ ҉͓͖̭͘t͒ͩiͪ̾n̍̉g͋ͫ͂ ̂̌t͒̽ͪeͦ̓s̅͆t̀̀͆ ҉̴̀i̇ͨńͧg̍̐ ͑̅tͯͯẻͧ ҉̮̰̦̕sͧ͊ ҉͍̫̹t̅͐i̋͋̋n͆͋g͐̄ ̓̚t͋̊ëͭs͐͐ẗ̔i͆ͦn̿̀g̃͊ ͐̎ͩtͥ̑̔ ҉̖̻ếs̄́͑ ҉̧̀ͅt̉ͨí̈ ҉̵̸n͗̚ĝ̌ ͬ̈ẗͧͬe̽͋̈sͧ̀t͋̿̆i͂̊nͦͫgͤ̑
t̄̈̿e̒ͨsͤ̚t͐̔i̐ͧn͆͋g̋ ̈̚tͩ̈eͭ̓sͬͪt̆̽͒i͂n͑̒g͛͆ ͪͨͥtͧ̅eͣ́sͮ̐t̒̃̆i̍͂n̏̔ ҉̨̥gͮͧ͛ ̿ͮt̓͐ ҉͓͙͕e͑͛s̒̉̉tͮ̔ ҉́͘i͑̈n͛̀g̿̄̀ ̃͗t̓̅ẽ͐s̀͊t̀͗iͬ͗ ҉̢͞n͊̑̌g̊͊̈ ́ͤt̓ͪeͫ͛sͨ̐t̽͑i̓̌n͊̓g̀͊ ҉̻̱ ͯͧt̾͂e̊̈s͗͂ͣt͛ͥi͌̃nͭͩğ̈
t̄ͧe̾̾ṡ͛tͮͩi̅͋nͦ̐ ҉̞̬gͩ̍ ̅̽ẗ̈̌ ҉͙͙̮͖eͤͧs̄ͮt̍͗i̓̏nͤ̎ġ̈ ͋̓̑̿t̅̄ë̚sͪ̂ ҉̯͜t̾ͨïͤn̏̔gͦͤ ͒̇ ҉͙̮t̃ͧeͥ̅sͨ̋tͯ͊iͭͣnͧ̋̐̄g͑̽ ͩ̃t͂̍e͌͐s̏̈t̔̾ ҉̵̘ͅi͂͒n̚g̉̎ ̉̀t̓̋eͤ͆ś̆́ ҉̷͕͕̹t͗̋ĭͯn̈ͩg̈̃ ͌̊̅ ҉̤̲͟tͦ̚e͗̇s͊̅ͣtͧïͫnͮͮ̊g̔̀
tͣ̓eͨ̆ ҉̭͇sͮ̆t͛ͥĩ͛ ҉̭̠̦̦͘ń͗͗gͩ̈ ͆̈tͥ̈͂e̓ͧ ҉̣̲̠ͅs͗̽̎͑t͊ͭ ҉̡̳͎̲í̈nͭͦgͭͧ ̅̆ ҉͙̕t͆̄e̿̆ ҉̜̱̠ͅsͯ̆ ҉̣͡tͥͩiͦ͑n͐̃g̀͊ ̓ͩtͫ̓͑ẽ̽s̈ͨt̂͊ǐ̅n̑̃g͛̓̾ ҉͠ ҉̰̖ ̅̄ ҉͖͠tͪ͗e̽̋s̈̓ͯtͥ̽ ҉̹̫iͬ͂nͫ̇gͪ́ ͨ̊t͑̿e͌ͪ ҉̶̖͝s̓͒ ҉̭͇͝t̋̽i̽̾͛ ҉ ҉ ҉̜̘͖͖n̊gͨ̈ ͣ͐ẗ̄eͤ͂̀s̏ͭt̄̓i̎̚nͤ̆g͋̅
# ....

and CPU goes to 100%.

Bug 🐛: using semantic-release overrides root scripts when not using workspaces

Unexpected Behavior:

"scripts": {
  "prepare": "husky install"
},

Expected Behavior

"scripts": {
  "dev": "npx tsc -w",
  "build": "npx tsc",
  "prepack": "yarn build",
  "test": "jest"
},

Failing Tests and CI on a fresh install

Bug description

A fresh install using npx create-prisma-generator has failing tests and CI runs.

To Reproduce

Screenshot for prompt questions answers:

Steps to reproduce the behavior:

Create a fresh project using the command above.
Navigate to packages/generator.
Run pnpm test (fails).
Push to a github repository (action fails).

Expected behavior

Test should be passing and github actions succeeding on a fresh install.

Screenshots

Environment & setup

OS: Linux
Node.js version: v16.13.1

Provide workflow instructions for how to develop / test your custom generator

Hi! Awesome project btw!

Is your feature request related to a problem? Please describe.

Spent about an hour digging through the source code to get a feel for how everything is working. Would be convenient to have explicit directions on how to make changes to the generator and test the updates. I'm now able to make changes and test them in the /usage directory, but tbh I'm still not sure if I'm technically using it correctly.

I feel like the documentation of the usage of the generated codebase is somewhat lacking.

Describe the solution you'd like

Documentation on the correct workflow for making changes to your generator and testing them. Right now my workflow is:

Make changes to /packages/generator/src/generator.ts
cd /packages/generator && npm run prepack
cd /packages/usage && npx prisma migrate

Not sure if there's an easier way, but that's what I arrived at via trial and error.

Could also provide a QOL script in the base directory's package.json:
"generate": "cd packages/generator && npm run prepack && cd ../usage && npx prisma generate"

Thanks again for your time making this great project!

Support introspection of @db tag

Is your feature request related to a problem? Please describe.

Currently i find no option to retrieve native database type with @db.SmallInt (for example).

Describe the solution you'd like

Not sure.

Describe alternatives you've considered

Not sure.

Additional context

At least support for PostgreSQL is enough.

Feature Request: Add an Eslint configuration

Is your feature request related to a problem? Please describe.

Inconsistency when working without Eslint in a project as a team.

Describe the solution you'd like

Add a default Eslint configuration to the root config files.

Upcoming rename of `@prisma/sdk` to `@prisma/internals` with Prisma 4

Hey,

Jan from Prisma Engineering here.

Quick heads up that we will soon rename our @prisma/sdk package to @prisma/internals with Prisma 4, which we plan to release on June 28th (soon!).

The @prisma/sdk package was meant as an Prisma internal package only, but somehow it leaked out over time and is now used across all kinds of tools - including yours of course 😄

With the rename of the Npm package we want to make it clearer that we can not give any API guarantees for @prisma/internals, might need to introduce breaking changes to the API from time to time and will not follow semantic versioning (breaking changes only in major upgrade) with it. We think that it is better communicated with internals than with sdk.
With Prisma 4, besides the package name nothing should change though.

Additionally it would be super helpful if you could help us gain an understanding where, how and why you are using @prisma/sdk (soon @prisma/internals, remember 😀) to achieve, what exactly. We want to cleanup that package and your feedback will be valuable to us to define a better API.

Looking forward to your feedback.

Best
Jan & your friends at Prisma

PS: Are you using Prisma.dmmf from import { Prisma } from '@prisma/client' in your code somewhere by chance? That will also change soon and not include the Prisma.dmmf.schema sub property. Instead you can use getDmmf from @prisma/internals moving forward.

Feat: Prisma 4 Support

Currently the package generated by this tool is built against Prisma 3.

Prisma 4 is now mature and so this package should either be deprecated or updated to support Prisma 4. This will mostly likely require ditching the exported logger object from @prisma/sdk in favor of using console.log directly. (Logger is only a chalk-colored wrapper around a vanilla log function)

Bug 🐛: scoped names for the package confuses mkdir

a name like this @cpg/prisma-generator-new should be transformed to cpg-prisma-generator-new when making the directory for it.

🐛 Bug Report: GitHub Actions should use the chosen package manager

Bug description

When creating the GitHub Actions, the default package manager that is selected (i.e., npm) should be added here as well. The current script, for example, relies on yarn and uses the yarn.lock file, which is - obviously - not present, if using npm.

Support for Primsa version 5

create-prisma-generator doesn't support Prisma 4 or 5 yet, it works only with Prisma 3.

Any contributions to support Prisma 4 in the create-prisma-generator are highly appreciated and will be part of the authors/contributors section of this tool.

Feature Request: Support Circle CI

Is your feature request related to a problem? Please describe.

Github Actions is the only supported CI workflow.

Describe the solution you'd like

Supporting Circle CI by providing the boilerplate configurations to automatically publish the Prisma generator to npm.

yassineldeeb / create-prisma-generator Goto Github PK

create-prisma-generator's Introduction

⚠️ Note

Prisma

Motivation

Also Created a blog on dev.to where we're gonna be discussing the hello world prisma generator together that this CLI has setup for you and the different concepts you'll come across when developing prisma generators, Check It out here

Usage

What’s Included?

Architecture

Prisma SDK reference

Community

Contributing

💚 All Thanks to Prisma's brilliant developers for making such an awesome Node.js ORM that can be easily built on top of it.

create-prisma-generator's People

Contributors

Stargazers

Watchers

Forkers

create-prisma-generator's Issues

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Bug description

To Reproduce

Screenshot for prompt questions answers:

Expected behavior

Environment & setup

Bug description

Environment & setup

Bug description

To Reproduce

Screenshot for prompt questions answers:

Steps to reproduce the behavior:

Expected behavior

Screenshots

Environment & setup

Bug description

Bug description

To Reproduce

Screenshot for prompt questions answers:

Steps to reproduce the behavior:

Expected behavior

Screenshots

Environment & setup

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Bug description

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Recommend Projects

Recommend Topics

Recommend Org