Replies: 3 comments 3 replies
-
|
Wow, what a list! Thank for the patches/interest! Lots of thoughts, typed quickly. Ignore typos please 😆. Also moving to discussion vs issue once I figure out GitHub buttons. A key goal for the projects: keep the template so it’s a quick “fork and go”. I don’t want to add a bunch of setup steps. It’s a template for capable devs to fork run with, not a one stop shop. I’m all for things that are easy optional extensions most projects need. I’m for adding features that are 1) likely to be needed by a wide range of saas apps and aren’t too specific, 2) don’t increase the mental load of working in the codebase, 3) don’t add extra setup steps. Optional steps that give you cool features, that are well isolated and can be ignored, aren’t too niche, and are safe from security POV: all for it. As an example, even though I recommend Cloudflare Pages, I keep the generic adapter so any platform works with zero config. My general workflow: build cool things on template, and back port when I think they could be useful to a lot of others. To answer your list:
Later things
Things that seem too niche:
Unsure:
|
Beta Was this translation helpful? Give feedback.
-
|
I agree with all your points. I'll see what I can do and then we take it from there. |
Beta Was this translation helpful? Give feedback.
-
|
@scosman do you want me to create an issue for the cookie port to track it? |
Beta Was this translation helpful? Give feedback.
-
|
@CharlBest Just a few lines, so ported it! a1c7dbd |
Beta Was this translation helpful? Give feedback.
-
|
I generally agree with what @scosman said, but one thing on my wish list would definitely be auth-helpers -> SSR, as Supabase seems to be fairly aggressively transitioning to SSR. If you want one more thing on a long list, that is :) |
Beta Was this translation helpful? Give feedback.
-
|
It seems the Leaked password protection feature is part of the Supabase Pro plan so wouldn't work for a starter like this. |
Beta Was this translation helpful? Give feedback.
-
I'm planning on using this starter for one of my projects and there are some things I want to add. Curious to hear if I should encapsulate some of them, that you would be interested in and make a PR(s). Before I do unnecessary work that you don't think fits into this project, here is a rough list I was thinking about.
Daisy UI:
<html data-theme="dark")Supabase:
JS/HTML:
navigator.share())<meta http-equiv="Content-Security-Policy")Additional:
Beta Was this translation helpful? Give feedback.
All reactions