fogbender / b2b-saaskit Goto Github PK

we can probably find a way to install less stuff in production build if we are going to use yarn install --production https://vercel.com/docs/concepts/deployments/troubleshoot-a-build#excluding-development-dependencies

I followed the setup process, skipping the OpenAI & Stripe setup. Love the process. I hit a couple of bumps, some of which were mine, and others were fixed already.

• The git (ssh) clone failed, so I redid with https. SSH might requires auth even for public repos? I've never used it before, so I've not yet run into this.
• Nit: The propelauth example project name is invalid (pwf-dev cannot contain -) (same in step 9) already fixed!
• The setup page marks step 6 as complete before I even do anything (noticed past step 3)
• Doesn't explain the flow of creating a posthog project. It could probably use a nod to follow the on-screen instructions, and which type of app to create (I assumed web)
• For step 9, you need to do propelauth before the supabase migration also looks to be fixed!

Hello

Apparently the db connection string to Supabase is broken.
On promptswithfriends after trying to create a prompt the following error appears:
getaddrinfo ENOTFOUND db.aajtsheydwqllesdmzzg.supabase.co

On my local machine I tried to follow the update guide but no success.

They recommend for drizzle:
export const sql = postgres(serverEnv.DATABASE_URL , { prepare: false });
with the new connectionString from db settings but that doesn't seem to fix the issue.

Any ideas how to fix this ?

how to setup something (or just use b2b saaskit)

• how to configure TailwindCSS in Astro without astro integration
• how to configure tRPC+React in Astro
• how to setup og images (with preview based on t3)
• ...

how to build simple apps using b2b saaskit:

• Integrate OpenAI
• add google analytics
• ...

move readme images from public/readme-images because they are ending up in the build output

For first-time contributors:

• this change is limited to how github includes images into markdown files, all of this could be done without running the app at all
• you can ask GPT :) https://promptswithfriends.com/prompts/vI31faeCLJHr-bGsGp9Fj

The PropelAuth service is currently experiencing downtime, leading to a 503 error being displayed when attempting to access the service. Users encountering this error are unable to proceed with authentication.

if I'm on https://promptswithfriends.com/app and I click on "create a prompt" or "prompts" it will redirect me back to /app, maybe it should redirect to /login instead

Ask users to pay us 50$ so that they don't have use use their own GPT token

let's hope this Twitter thread will have some answers 🤞 https://twitter.com/JLarky/status/1661803851459211265

we need to create session id that will allow posthog correlate when the same session is continuing instead of creating new one every time

this will allow us to better document prompts, comment messages are not going to be sent to API

A developer is likely to have an existing prompt buried in code, in JSON format. It would be great to be able to import a prompt from a JSON string.

We need to find a way to cover testing use case. Options:

• vitest
• playwright
• checkly

should be easy, right? :)

update: I found this https://github.com/JoshuaKGoldberg/joshuakgoldberg-dot-com-next

TRPCError: Could not validate access token.
    at eval (/.../b2b-saaskit/src/lib/trpc/trpc.ts:91:11)
    at async callRecursive (file:///.../b2b-saaskit/node_modules/@trpc/server/dist/index.mjs:452:32)
    at async callRecursive (file:///.../b2b-saaskit/node_modules/@trpc/server/dist/index.mjs:452:32)
    at async resolve (file:///.../b2b-saaskit/node_modules/@trpc/server/dist/index.mjs:482:24) {
  code: 'UNAUTHORIZED',
  [cause]: UnauthorizedException [Error]: jwt malformed
      at verifyToken (/.../b2b-saaskit/node_modules/@propelauth/node/dist/index.js:23063:19)
      at /.../b2b-saaskit/node_modules/@propelauth/node/dist/index.js:23039:16
      at Generator.next (<anonymous>)
      at fulfilled (/.../b2b-saaskit/node_modules/@propelauth/node/dist/index.js:37:58) {
    status: 401
  }
}

it looks like set-cookie header doesn't work in Node 19, but it was working in 18 and was fixed in 20

nodejs/node#47755

We are calling ctx.resHeaders.append('set-cookie', ...) twice and only one of them would be applied in Node 19.

It looks like that in 19:

And it looks like this in 18 or 20 (you see two cookies set):