feat: supabase

[manuel3108]

Notes:

• shoutout to @mstibbard for the initial pr against svelte-add. I tried patching in his changes, which obviously only worked to some degree. But at least git recognizes that he authored those commits now
• adds a new scripts section to the adder config. Can be used to execute external npx commands and can be used together with our file-based approach (also initially implement by @mstibbard)
• removes integrationType: 'external' and integrationType itself from the config, as it now got kinda redundant.
• the only adder using integrationType: 'external' was storybook. it was migrated to use the new scripts section

[AdrianGonz97]

this thing is an absolute behemoth. unfortunately i ran out of time today as well, but i'll aim to finish up in the morning!

i'd also like to add that i'm starting to have some reservations about the inclusion of this adder though. the many features that it provides are very cool and i can see how someone can move fast with it, but it's also fairly complex!

i worry that we may be leaning too far into the "opinionated for a particular product" territory (i.e. the reason we don't include any component libraries).

i wonder if this would be better suited as a community adder? im not sure yet

[manuel3108]

I do agree that there is a lot to digest here. The thing is that probably about 60% of the code belong to the demo. All the other options have a pretty low impact code wise iirc.

I do not think we should make it a community adder at this point. We can always try to find someone later, I do think having it is a benefit.

As for the code I was thinking this morning, if it would be smart to have another file called demo.ts or something which also declared a variable with the defineAdderConfig helper function. Then we could spread in the relevant parts as needed, that should already make it easier to reason about the code

[AdrianGonz97]

As for the code I was thinking this morning, if it would be smart to have another file called demo.ts or something which also declared a variable with the defineAdderConfig helper function. Then we could spread in the relevant parts as needed, that should already make it easier to reason about the code

i like this idea, though we should keep it pretty simple. we shouldnt need any helper functions if we just type annotate it:

// demos.ts
export const demos: FileType<typeof options>[] = [
	{
		name: () => 'some-demo-file.svelte',
		contentType: 'svelte',
		content: () => { ... }
	},
	...
];

[manuel3108]

This was from my phone this morning, where i was assuming we also have some packages that are only necessary for the demo, but that's not the case.
Working on this

[benmccann]

I wonder if it's possible to shrink down the demo at all. I can't really tell as I'm on my phone, but could we just put an empty file with a comment showing where to put migrations instead of making a notes table and for an example query maybe hit some built-in table? The potential wrinkle on the last part is I'm not sure if the user would have permission to hit the system catalogs or not, but if there is one they have access to it could help simplify things

[manuel3108]

Just had a look at this but i doubt this possible, if we want to keep the demo working, which kinda is the goal

[AdrianGonz97]

since we've decided that the supabase adder would be better as a community adder, we'll need to merge everything in this PR besides the supabase specific code.

we could either break it out into a separate PR or we can delete the adder here and merge this one. i'm fine with either, so whichever is easiest!