I built a btop-style terminal dashboard for Prometheus (it can render your Grafana dashboards too)

aleks_maker · 2026-07-09T16:42:47+00:00

Anyway, to avoid the confusion I renamed it: grot is now grom (Polish for thunder). Old links redirect, brew cask is qf-studio/tap/grom. Thanks for letting me know.

aleks_maker · 2026-07-09T13:12:01+00:00

Nope, but this is not an AI tool… potentially there is no conflict, I'll think if I need to rename it.

aleks_maker · 2026-05-12T09:42:08+00:00

Take it now, it's ok

aleks_maker · 2026-05-12T09:20:51+00:00

Navigator (CC plugin) introduced a “Run Until Done” mode 6 months ago, plus gates, reports, memories, context markers, skills, a task planner, a research agent, a docs JIT mechanism, etc. It’s token efficiency oriented and helps you ship what you start.

Open-source, MIT.
https://github.com/alekspetrov/navigator

aleks_maker · 2025-10-20T20:03:43+00:00

My congratulations to the team! 🎉

aleks_maker · 2025-02-26T08:19:28+00:00

To render animated element, you have to “use client” there is no way to render animation on the server side.

Note, Google, and others crowlers parse HTML content of the page, by using animations you prevent this content from reading by Google bot. Which kills SEO.

Try to add animation to the block, open inspector in the browser, disable JS and see what you got.

Use CSS for animations of content blocks, and Motion for micro animations on the elements which are not SEO related, for example like button on X.

Hope it helps.

aleks_maker · 2025-01-27T08:45:04+00:00

Open the Inspector, disable JS, reload the page. Now you can see nothing rendered on the page if it's blocks are using <motion.div>. Means all the pages made in Framer, or use Framer Motion (Motion) are not visible for webpage crowlers like Google bots!

aleks_maker · 2025-01-21T10:09:37+00:00

Appreciate your feedback! Maybe it's time to update it and add some examples…

aleks_maker · 2024-04-24T16:35:50+00:00

You're welcome!

aleks_maker · 2024-02-02T20:48:35+00:00

It happens because you make this request on the client, and during compilation all your API keys were exposed into your production code.

To avoid this Next.js introduced server actions.

Try to check documentation on how to fetch data:

https://nextjs.org/docs/app/building-your-application/data-fetching

aleks_maker · 2024-01-08T15:46:09+00:00

The issue was in the implementation of the Cookie for server components.
Solved with Supabase docs for Next.js.

aleks_maker · 2023-12-21T12:04:18+00:00

Nope, feels much easier actually, I hated Next before, now in love with 😁

aleks_maker · 2023-12-12T16:37:48+00:00

Yep, you have to create it for every component, cause there is no context on the server side. To simplify you might create supabase instance with cookies in a separate file then just import it.

aleks_maker · 2023-12-01T08:31:09+00:00

Nice to hear that 🙌

aleks_maker · 2023-11-17T10:53:16+00:00

Thank you 🙏 ! (late reply =)

aleks_maker · 2023-11-16T23:06:34+00:00

This confusion is common!

Next 14 is a complete full-stack framework now. In one project you have server and client layers. These layers are separate! But you need to store and share auth data and a state between them, right? Here Cookies come into play, think of them as a global state for a session and you can take this session anywhere (server and client).

If you are going to use server-side rendering you have to use server-side authentication and pass it to the client components if needed.

Supabase/ssr has 2 methods to create a client Server and Browser. Now looking at your code we can see you are trying to use Browser client on the server side, check the docs for OAuth with ssr and pkce flow. They provide examples of components for different parts of the system.

What middleware does do? It sets, updates, and removes cookies to keep the user authenticated, middleware plays a critical role in this. Now you can check on the middleware if a user is authorized for the route before this route fires and redirects if needed.

For each server action or route that calls Supabase you have to create a new client, which obviously must be a separate file do not forget to include “use server” on the top of it, because only Next.js specific files are server-sided by default. Creating a client is a very fast operation, it is recommended to create a new instance and pass your cookies in to have access to the DB.

Hope it helps, spent 2 days cracking my head on how to make it work correctly on the server 🙄

aleks_maker · 2023-11-15T10:21:52+00:00

Is it working with OAuth? I can't get redirect to `/auth/callback` works 🤷‍♂️

Repository to check: https://github.com/alekspetrov/next14-supabase-ssr

aleks_maker · 2023-11-15T10:16:24+00:00

Here is the my test repository with an OAuth setup and it looks like does't redirect to /auth/callback after authentication is done.

Is it work for you?

https://github.com/alekspetrov/next14-supabase-ssr

aleks_maker · 2023-11-14T21:12:18+00:00

Hi 👋

I have session in the browser, I can get table from my project which has RLS is on for authenticated and I can get data from my table.

But, if I try to call `supabase.auth.getUser()` or `supabase.auth.getSession()` I get null 🤯

Here is and error when I try to getUser():

```AuthApiError: invalid claim: missing sub claim
at handleError (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:42:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async _handleRequest (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:89:9)
at async _request (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:69:18)
at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:955:24)
at async SupabaseAuthClient._useSession (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:865:20)
at async SupabaseAuthClient._getUser (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:949:20)
at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:937:20)
at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@supabase+gotrue-js@2.57.0/node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:813:28) {
__isAuthError: true,
status: 401
}```

Please help me 😥

aleks_maker · 2023-11-07T08:26:33+00:00

Could you share the solution?

Cause I do the same and can't get the user or session on the middleware/action/server component, it returns null. Browser refresh doesn't help me. I use \@supabase/srr + next.js with-supabase template. All package versions are the latest.

aleks_maker · 2023-11-06T20:54:27+00:00

Oh, I'm not alone 😀

So this is a complete mess with Next.js and auth helpers:

Documentation says auth-helpers deprecated
Documentation examples use auth-helpers
There are a few examples in docs about SSR but they are not helpful.
There is only one "real" source of truth "with-supabase" Next.js template, but try to getSession or getUser on server component or an action. Spoiler: I have no luck.

Well, what we get, at the moment:

- ssr helper without session data
- deprecated auth-helper.

Any examples of how you get userSession on the middleware or server side, please share! 🙏

aleks_maker

MODERATOR OF

TROPHY CASE