Ben Holmes

@robertvanhoesel Ah ha, I didn't realize you were importing the action back into your `index.ts` file. Yes, I'd expect that to work. Exporting from Astro components _can_ cause bundling issues...

I agree with Blu on the ordering! I also have a question on API design. Astro DB uses a base function with an object parameter (`column.number({ optional: true })`), while...

Good questions here! I agree with Ema that `addMiddleware()` _can_ simplify configuration for the developer. I would only go this route if a majority of users will grab the "out-of-the-box"...

Oh ho ho, did somebody say `build.write: false`? That's how we server render components in Slinkity today! I think expanding this usage to HTML parsing could aid in serverless as...

Also, an important caveat I want to mention: Vite production builds aren't the _fastest_ around. Since they target HTML files as the entrypoint and could compile SCSS files on-the-fly as...

Also want to call out that Astro has 100% ruled out Vite in a serverless environment. Any bundling or analysis of non-JS assets occurs at build time, while frontmatter (essentially...

@AleksandrHovhannisyan So it's not _impossible,_ just not recommended as the only option. the length of Vite builds and the size of the bundle make it a no-go for certain use...

Thanks for starting this thread! We wanted to explain the `navigate()` function exposed by `astro:transitions`, but realized there's no proper API reference ([only a guide](https://docs.astro.build/en/guides/view-transitions/#trigger-navigation)). It sounds like we're exploring...

Thanks for the issue @gitjoshu! Unfortunately, http://localhost:4321/ isn't super helpful for me to reproduce 😛 Is it possible to replicate in a stackblitz environment using one of our [astro templates?](https://astro.new)

@gitjoshu haha totally fine! appreciate that Stackblitz environment. I'll admit I've been putting these issue logs on the backburner between travel weeks and Astro's launch week, but know that I'm...