Prisma ORM: be more explicit about what to skip#31013
Merged
mao-sz merged 2 commits intoTheOdinProject:mainfrom Apr 22, 2026
Merged
Prisma ORM: be more explicit about what to skip#31013mao-sz merged 2 commits intoTheOdinProject:mainfrom
mao-sz merged 2 commits intoTheOdinProject:mainfrom
Conversation
mao-sz
approved these changes
Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Because
Learners including me was getting confused on what specific commands to skip.
And regarding step 3 I did’t want to be extremely verbose and state to learners that you can skip updating your package.json file because node auto detects your module system depending on the syntax, or explicitly state that you should follow Prisma Quickstart and update the package.json file to
type: "module", because explicitly stated then it would raise questions about why. Which to be realistic since we’re not using TypeScript it doesn’t matter if the module system was ESM or CJS.This PR
npm initcommand used in Prisma QuickStart.@types/nodein step 2 because Prisma Quickstart doesn’t install the packageIssue
Closes #31011
Additional Information
Discord thread that led to this issue being created: https://discord.com/channels/505093832157691914/597796701650026517/1496387459750301697
Pull Request Requirements
location of change: brief description of changeformat, e.g.Intro to HTML and CSS lesson: Fix link textBecausesection summarizes the reason for this PRThis PRsection has a bullet point list describing the changes in this PRIssuesection