Trek Glowacki comments

Results 45 comments of


                                            Trek Glowacki

Sharp.js v0.33 not working in combination with pnpm

This appears to have been a specific interaction between next and sharp. https://github.com/vercel/nft/pull/387 should be the fix. Feel free to let us know at [vercel/next.js](https://github.com/vercel/next.js) if it doesn't!

[cli] tidy up some command structures

@TooTallNate 🫡

Can't get vercel to deploy a `go mod vendor`-ed project

@arisudesu thanks for reporting this. We'll give it a look.

Fix/Prevent erounus Next.js API route warning, on non-Next.js apps

Hi @Lissy93, this looks good but there some goofy issues with us accepting outside contributions (basically, our tests won't run correctly on forks). I pushed up your code here https://github.com/vercel/vercel/pull/11987...

`vercel link --repo` very slow

@vjpr oh yeah, that's bad. There are other uses for `getWorkspaces` besides the CLI, but in our case we simply forgot to pass along project root path when we call...

`vercel link --repo` very slow

@vjpr could you open your second comment as a new issue. It doesn't seem relate to this one.

`vercel link --repo` very slow

@vjpr I'm having trouble reproducing what you're seeing. Is this related to something specifically defined in your app? `getWorkspacePackagePaths` uses globs (via `getPackagePaths`), but as far as I can see...

`vercel link --repo` very slow

We can't quite reproduce this issue. If someone can list steps to repro, please comment and reopen.

Vercel build hang when have both app router and page router

Hi @nnhuyhoang, Thanks for reaching out! We use this Issue tracker for bugs in the Vercel CLI and related open source libraries. For general platform help and feedback please open...

vercel remove --safe no longer preserving rollback deployment

Hey @cosn, If you have a fix already identified that would be great, otherwise we can dig in.