cli VS analog

Recently, I noticed that in our remote project, the database storage schema has a migration not present when one sets up the local stack for development. Upon inspection, the Supabase CLI uses an old version of the storage image. Currently, there is no way to change this (that I know of) until the CLI team updates the CLI to use this version.

@doganugurlu Looks like Deno team implemented a fix https://denostatus.com/cllm0jzq219036bjottk03k2ac Are you still experiencing the issue?

We used to cache the modules locally, I will need to check if we made any configuration change. Can you kindly open an issue for Supabase CLI - https://github.com/supabase/cli/issues

> Oh, I had no idea that the functions routes were "wild card"! I don't think that's mentioned anywhere in the documentation, btw.

Good point! will update the docs.

> Sorry, I actually mean "import-maps": https://github.com/supabase/cli/issues/1338

I'll take a look at this issue. We've improved import map resolution in the last couple of CLI releases. But it looks like there are more edge cases.

We’ve moved the Supabase CLI to a fortnightly stable-release cycle. Every 2 weeks, we will update the latest tag on npm, the supabase/tap for homebrew, and the supabase scoop bucket. You can find the binary downloads in our GitHub latest release.

I think we've been working on that recently here: https://github.com/supabase/cli/pull/907

Can you try it locally with the supabase CLI? https://github.com/supabase/cli

For more info see this issue on GitHub.

I opened a Github issue: https://github.com/supabase/cli/issues/939, but I figured I'd see if any of you hit this and, hopefully, got past it.

Are there plans to support connections to self hosted remotes (to deploy to self-hosted instances, for example) with the cli? https://github.com/supabase/cli/issues/753

The errors you cite come from the https://github.com/supabase/cli not from postgREST(it does support v15).

Visit and Star the GitHub Repo

We have also introduced a new Single File Component format in Analog for authoring components and directives. What started as a .ng file extension for components and directives using Angular has evolved into the Analog SFC, along with features including support for auto-imports, inline markdown templates, page routes, and more. We are continuing to iterate on this approach, and exploring options to enable this format in Angular applications as the future of Analog progresses.

Use Netlify if you want Edge deployment, otherwise AnalogJS is freaking amazing and solves all the problems above. Sponsor AnalogJS the project if you can give a few bucks!

Umm, ng templates look awesome! Let's get it working like a charm!

If you'd like to take Analog for a spin, check out this blog post on Building a Blog with Analog and Angular. If you want to get involved in the project, check out the GitHub repo.

Where an average contributor may contribute to one project during their career, we see an opportunity to highlight those contributions and share your experience with others. We would love to see your highlights, whether you are starting in open-source or the core maintainer of analog.

Visit and Star the GitHub Repo

Feature: Use NestJS integration as SSR/http server #317

Vitest and Angular is actually already possible! Check out AnalogJs if you are interested in how it works: https://github.com/analogjs/analog

I'm thrilled to see my project (https://mockoon.com) being part of this first cohort! It's a great opportunity but it's also good for open-source projects in general. It can only contribute to make our industry more sustainable.

Here is the list of the 20 projects that have been selected:

- https://github.com/analogjs/analog: Analog is a fullstack meta-framework to build applications and websites with Angular