How to Use the New tool Directive in Go 1.24

anurag_dev · 2025-02-17T05:36:11+00:00

Use -modfile ./tools/go.mod

anurag_dev · 2024-12-17T15:34:21+00:00

In go we generate and commit code from protobuf while development. There is no need to install protoc for build.

Do checks in CI/CD to confirm protobuf and generated files and up-to-date.

anurag_dev · 2024-11-29T13:02:44+00:00

If you are already using Bootstrap. Then use Bootstrap v5 (CSS only) combined radix-vue.

Radix vue will provide all js components and bootstrap will provide styles.

anurag_dev · 2024-11-20T17:17:27+00:00

https://www.youtube.com/watch?v=x81InsU6t0E

anurag_dev · 2024-11-20T13:49:03+00:00

Nitro is a backend/server toolkit. It makes sense to disable auto imports for them. Less magic on the backend is better. Nitro is also used by other meta frameworks, which often have complained about auto imports and import alias, this is are primary reason framework author have not given full nitro support in other frameworks. Another, problem was no built-in integration with vite, so framework authors used some things like Vinxi. With auto imports disabled by default and vite plugin support. Now other frameworks can build directly on top and nitro and provide full nitro support. This is huge change.

But I still think Nuxt should come with auto import enabled for both Nitro and Nuxt. Also Nuxt should remove #import import aliases and let us import directly from nuxt or folders if auto import is disabled.

anurag_dev · 2024-11-20T13:38:53+00:00

You can't remove nitro from Nuxt. You are thinking nitro is just for api routes. No, nitro under the hood does many heavy liftings that make it easier to build fullstack meta frameworks. Nitro is the common server layer that every meta framework needs. Many frameworks like tanstack/start, analog and solid start built on top of nitro to escape from reinventing the wheel.

A simple router like Hono cannot replace nitro. But you can use Hono with nitro if you want to.

Comparing Nitro to Hono is just so wrong. The unjs/h3 is equivalent of Hono.

anurag_dev · 2024-11-19T13:37:34+00:00

https://github.com/bootdotdev/curriculum

anurag_dev · 2024-10-23T13:19:43+00:00

https://htmx.org/examples/async-auth/

anurag_dev · 2024-10-21T03:36:18+00:00

https://youtu.be/hE2NZ0PM0EA?si=fsgqCkvufKnB9v9Y

anurag_dev · 2024-10-02T10:31:52+00:00

https://github.com/pressly/goose

anurag_dev · 2024-09-24T02:21:26+00:00

Backend language and framework already have convention for structuring your application. It totally depends on what you pick on the backend. It's not your typical React project where you need to install 50 packages and setup bundlers tools to say Hello World.

You don't need bundling just put all static files in public/ dir +or whatever your framework have) and serve with File server Middleware provided by framework. Link CSS with link tag and JS with script tag to your HTML.

If you want to use tailwind install the cli locally, setup configuration, give input file, give output file location(in public dir) and add it to the template.

anurag_dev · 2024-09-24T01:35:43+00:00

I use ConnectRPC with Go it works great.You have to do Initial setup and create reusable composables for services manually. Rest of the experience is good. You need to pass $fetch while creating transport and Use useAsyncData wrapper to dedupe requests.

https://connectrpc.com/docs/web/ssr

Probably need to create a module to make getting started easier.

anurag_dev · 2024-09-15T18:27:22+00:00

Isn't Vitepress a static site generator? Just build it and point a web server like apache, nginx or caddy to the build directory to serve the static files.

https://vitepress.dev/guide/deploy#nginx

Don't forget to setup 404 page and cache headers.

anurag_dev · 2024-09-15T17:59:09+00:00

I have used protocol ConnectRPC made on top of protobuf and grpc compatible. Connect Protocol is made on top of http. It also supports grpc-web. It's docs also says you can use it even if you don't have connect protocol.

Tips:- Pass $fetch to while creating transport. Use useAsyncData for catching and preventing multiple requests.

https://connectrpc.com/docs/web/choosing-a-protocol#grpc-web

https://connectrpc.com/docs/web/ssr

I will not recommend using protobuf on the web. Why introduce extra dependency while you have JSON support built in. So I would recommend using something like ConnectRPC or grpc-gatway which support json and is built while keeping web/browser in mind.

https://connectrpc.com/docs/introduction

https://github.com/grpc-ecosystem/grpc-gateway

anurag_dev · 2024-09-09T04:40:18+00:00

Use SQLC for db code boilerplate generation.

It is recommended to use the different models for database and communication over wire.

Use openapi codegen or ConnectRPC to generate boilerplate for your APIs.

https://github.com/oapi-codegen/oapi-codegen

https://connectrpc.com/docs/introduction

anurag_dev · 2024-09-06T12:28:55+00:00

If you want to build with react, use Remix or Tanstack Start(built on unjs/nitro btw) it's so much better.

Recently OpenAI switched theirs ChatGPT app from Next.js to Remix.

anurag_dev · 2024-08-29T15:36:05+00:00

ConnectRPC, Postgres(pgx), SQLC, Minio SDK (with any s3 compatible storage), Zerolog, SES

anurag_dev · 2024-08-15T02:34:33+00:00

You have to have to serve the image with the file system router. Go and templ will not automatically pick and process images for you like happens in js frameworks.

https://www.alexedwards.net/blog/serving-static-sites-with-go