Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot create project with pnpm #8744

Closed
rburgst opened this issue Aug 8, 2023 · 4 comments
Closed

cannot create project with pnpm #8744

rburgst opened this issue Aug 8, 2023 · 4 comments
Assignees

Comments

@rburgst
Copy link
Contributor

rburgst commented Aug 8, 2023

pnpm create keystone-app
# name it `test-pnpm`
cd test-pnpm
rm -rf node_modules/ package-lock.json
pnpm install

Expected

The project should be able to install and build properly

Actual

pnpm install
 WARN  deprecated cuid@2.1.8: Cuid and other k-sortable and non-cryptographic ids (Ulid, ObjectId, KSUID, all UUIDs) are all insecure. Use @paralleldrive/cuid2 instead.
 WARN  deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
Packages: +895
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: /Users/rainer.burgstaller/Library/pnpm/store/v3
  Virtual store is at:             node_modules/.pnpm
Progress: resolved 924, reused 894, downloaded 1, added 895, done

> keystone-app@1.0.2 postinstall /Users/Rainer.Burgstaller/git/private/test-pnpm
> keystone build --no-ui --frozen

✨ GraphQL and Prisma schemas are up to date
npm ERR! Cannot read properties of null (reading 'matches')

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/rainer.burgstaller/.npm/_logs/2023-08-08T06_39_56_721Z-debug-0.log
AggregateError:
    Error: Command failed with exit code 1: npm install -D prisma@latest

This part is probably a duplicate of #7066.

However then I try to upgrade everything to the latest version

grafik
pnpm install
Lockfile is up to date, resolution step is skipped
Already up to date

> keystone-app@1.0.2 postinstall /Users/Rainer.Burgstaller/git/private/test-pnpm
> keystone build --no-ui --frozen

✨ GraphQL and Prisma schemas are up to date
 WARN  deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
Packages: +2
++
Progress: resolved 907, reused 876, downloaded 2, added 2, done
node_modules/.pnpm/@prisma+engines@5.1.1/node_modules/@prisma/engines: Running postinstall script, done in 3.3s
node_modules/.pnpm/prisma@5.1.1/node_modules/prisma: Running preinstall script, done in 39ms

devDependencies:
+ prisma 5.1.1

Done in 12.4s
 WARN  deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
Packages: +2
++
Progress: resolved 909, reused 878, downloaded 2, added 2, done
node_modules/.pnpm/@prisma+client@5.1.1_prisma@5.1.1/node_modules/@prisma/client: Running postinstall script, done in 61ms

dependencies:
+ @prisma/client 5.1.1

Done in 9.5s

✔ Installed the @prisma/client and prisma packages in your project
Done in 25.8s

when I then try to build the app, it hangs

pnpm build

> keystone-app@1.0.2 build /Users/Rainer.Burgstaller/git/private/test-pnpm
> keystone build

✨ Generated GraphQL and Prisma schemas
✨ Generating Admin UI code
✨ Building Admin UI
- warn You have enabled experimental feature (appDir) in next.config.js.
- warn Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

- info Skipping validation of types
- info Skipping linting
- info Creating an optimized production build
- info Compiled successfully
- info Collecting page data
- info Generating static pages (15/15)
- info Finalizing page optimization

Route (pages)                              Size     First Load JS
┌ ○ /                                      1.62 kB         475 kB
├   /_app                                  0 B             474 kB
├ ○ /404                                   181 B           474 kB
├ ○ /init                                  6.45 kB         480 kB
├ ○ /no-access                             407 B           474 kB
├ ○ /posts                                 241 B           483 kB
├ ○ /posts/[id]                            243 B           478 kB
├ ○ /posts/create                          1.45 kB         475 kB
├ ○ /signin                                1.56 kB         475 kB
├ ○ /tags                                  240 B           483 kB
├ ○ /tags/[id]                             244 B           478 kB
├ ○ /tags/create                           1.45 kB         475 kB
├ ○ /users                                 240 B           483 kB
├ ○ /users/[id]                            244 B           478 kB
└ ○ /users/create                          1.45 kB         475 kB
+ First Load JS shared by all              474 kB
  ├ chunks/framework-6dab90d1d72e725d.js   45 kB
  ├ chunks/main-4efae77ba108670e.js        27.8 kB
  ├ chunks/pages/_app-475472aa75686854.js  400 kB
  └ chunks/webpack-880e48e2fc817058.js     1 kB

○  (Static)  automatically rendered as static HTML (uses no initial props)

after that is just hangs there (for 15+ minutes).

context

node -v
v18.16.0
@dcousens dcousens self-assigned this Aug 8, 2023
@borisno2
Copy link
Member

borisno2 commented Aug 9, 2023

I am having the same issue when updating next to 13.4.13 - borisno2/on-the-hill-drama-club#136 Vercel build timing out after 45mins.

Could be a similar next build issue to what was happening in #8412

@nedgar
Copy link

nedgar commented Aug 9, 2023

See suggested workaround: #8581 (comment).

@rburgst
Copy link
Contributor Author

rburgst commented Aug 23, 2023

this seems to work but as I am building in a workspace I am facing #8782

@rburgst
Copy link
Contributor Author

rburgst commented Aug 31, 2023

The workaround works, closing, however, obviously it would be cool to not need this workaround in the first place.

@rburgst rburgst closed this as completed Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants