8 Replies
unfortunately no, if you open a feature request (https://github.com/cloudflare/next-on-pages/issues/new?assignees=&labels=enhancement&projects=&template=feature-request.yml&title=%5B%E2%9A%A1+Feature%5D%3A+) on next-on-pages I will look into enabling (I can't remember if there was a technical limitation around that though.... 🤔)
you can use other package managers though, I'm pretty sure that
yarn and pnpm only warn you about conflicting peer dependencies without making the installation faili opened up the issue, you also cant seem to run --force inside the actual build in the worker config as well which ive brought up in another thread. the only reason im chasing this is Lucia + Prisma Edge have a dependency conflict since the latter is in preview so its a rare case
thanks! I'll look into it as soon as I can 🙂
you also cant seem to run --force inside the actual build in the worker config
can't change the build command here to use --force either but i was told it was being looked into
ah I see 🤔
you mean as the standard npm initialization right?
I can look into that.... I'd imagine that the pages CI performs an
npm ci I guess that that should work fine with a package-lock created using --force... is that not the case? 🤔so an .npmrc with force=true solved both issues fortunately
new bug
so i managed to get things sort of working after 2 days
i'm not the most experienced so i feel like others coming to cloudflare from vercel similar to me can benefit from the docs letting them know they need to restructure the way they set up routes and such - just a suggestion