nagman

Here, I've renamed it to `mobileFirst` and it's a boolean, now

Would be nice to use keywords like `>=` and `

I've made a PR with a new `strategy` option in the config, which allows us to opt for mobile-first mode. It replaces the media-queries with a min-width syntax, and sort...

Not sure if it's related, but `autopause` doesn't work neither. Maybe because I'm using next.js? Could it have to do with SSR, or script loading? I've seen other issues with...

Apparently the `autopause` issue is being addressed in another thread: https://github.com/vimeo/player.js/issues/714

I've noticed something (maybe not related), but I get different results whether I run `prisma generate` or `prisma deploy`. With `prisma deploy`: **generated/prisma-client/index.ts** ``` // Code generated by Prisma ([email protected])....

@pantharshit00 What do you mean by passing the secret to prisma client? Doesn't prisma already handle this, according to https://www.prisma.io/docs/prisma-server/authentication-and-security-kke4/#prisma-services? > Also note that prisma generate automatically injects the secret...

It's already done by the prisma generator. Here's the end of `generated/prisma-client/index.ts`: ``` export const Prisma = makePrismaClientClass({ typeDefs, models, endpoint: `http://prisma:4466`, secret: `${process.env["PRISMA_SECRET"]}` }); export const prisma = new...

OMG! I solved it thanks to your pointing :smiley: The fact was that `PRISMA_SECRET` was not provided as an environment variable to my API in `docker-compose.yml`. I added it: ```...

> To make matters even worse, I get the same Your token is invalid. even when I don't have any secret set at all. That's very odd, I've never had...