Tags: prisma/prisma
Tags
fix: use absolute path file URL for subcommand loading (#27199) Prior to 6.8.1, the subcommand loading mechanism was failing on Windows because it was using an absolute path without the `file://` protocol, making the disk name looks like a protocol and thus the whole path becoming an invalid URL. In 6.8.1, this was worked around by using a relative path, but this again broke on Windows if the CLI installation path and the subcommand temporary directory are on different drives. The correct fix for the issue is to use a `file://` URL with the absolute path to the subcommand. This was not done in 6.8.1 because it broke the tests. However, the reason that broke the tests was not in our code, but in Jest itself, which has atrocious ESM support and doesn't know how to handle the `file://` URLs. This commit fixes the issue by using a `file://` URL for the absolute path, and changes the `SubCommand.test.ts` test to run under Vitest instead of Jest. Going forward, we can gradually migrate the rest of the tests to Vitest. Fixes: #27195 Closes: https://linear.app/prisma-company/issue/ORM-983/bug-subcommand-esm-module-resolution-fails-on-windows
feat: ORM-941 create credentials store package (#27171) Adds a dedicated package to handle credential storage for our CLI and VSCode extension. As per the described in https://www.notion.so/prismaio/Technical-Design-10xPPg-VSCode-Extension-1ea9e8aecef780ee94c4e555c8bc568b
chore: prisma postgres init copy changes (#26229) * updates * lock * conditional db url printing * minor * little better error handling * copy changes * fix prettier breaking conditional logic * update snap due to line break changes * copy updates from review * revert the default output to version 6.2.0 * revert snap change * refresh snaps * fix(test): update cli snapshots --------- Co-authored-by: jkomyno <12381818+jkomyno@users.noreply.github.com>
PreviousNext