keystone icon indicating copy to clipboard operation
keystone copied to clipboard

Postinstall does not respect package manager

Open sladg opened this issue 3 years ago • 1 comments

Steps to reproduce:

  • create new project,
  • use pnpm install,
  • postinstall script will run with npm generating package-lock.json and messing up versions (prisma binaries).

I'm not able to get pnpm working as I'm either facing problem with npm vs pnpm or Prisma binaries / schema not getting generated properly in case I ignore postinstall hooks.

Screenshot 2021-12-09 at 20 50 55

Would be super useful to have guide for manual post installs steps so in case of any issues, we can run those manually instead of relying on keystone postinstall.

sladg avatar Dec 09 '21 19:12 sladg

Hi @sladg,

Thanks for the report, I'll investigate this with the team.

bladey avatar Dec 20 '21 06:12 bladey

I cannot reproduce. My steps

mkdir issue-7066
cd issue-7066/
pnpm init
pnpm install @keystone-6/core
vim keystone.ts
import { config } from '@keystone-6/core'

export default config({
  db: {
    provider: 'sqlite',
    url: 'file:./keystone-example.db',
  },
  lists: {},
})
$ pnpm keystone dev
✨ Starting Keystone

Happy to re-open if anyone can reproduce and comment with steps

dcousens avatar Nov 14 '23 00:11 dcousens