Jeff See

@zeeg Got it, thanks. One of the gotchas we'll soon be removing is that you need that `'hono'` import. We use that to find an entrypoint file, but in the future we'll just treat a server.ts as the entrpoint, if it exists. Good feedback RE: unhelpful error messages, will address!

@jeffsee_ github.com/getsentry/juni… closest thing to representing what im deploying fwiw

update: yes i will

@zeeg I'm wondering if your project's framework isn't being picked up, if you look in Settings -> Build and Deployment you should see a Framework Settings section. That should be Nitro, or Hono if you want to try it without Nitro

@jeffsee_ also seems there might be concerns w/ pnpm and monorepos when using these? at least thats where claude is right now i was gonna just swap hono to literally anything as i dont care (e.g. express) but im guessing ill hit similar issues

@zeeg 👋 are you using the nitro@3 beta with vite? You should be able to add a `server.ts` file like the example here nitro.build/examples/hono What kind of error are you seeing?

seems like vercel is still not straight forward for anything thats not a static website / next.js

@ggaler7 Give Vercel CLI skills a try! skills.sh/vercel/vercel/…

opus 4.6 is so bad with using vercel cli and the railway gql api

@GustavoValverde @rauchg @ChristoRibeiro @vercel_support The issue was `vercel dev` wasn't respecting your installed version of Typescript, that's been fixed in the lastest version (48.4.1) of the CLI. We may turn off typechecking altogether during 🤔

@rauchg @ChristoRibeiro @vercel_support community.vercel.com/t/vc-dev-fails…

.@vercel_support is it possible to use Bun 1.3 during the build? I see bun v1.2.23 is used and no way to change it. cc @rauchg

@WebTwitr @cramforce @ctatedev @andrewqu @vercel Are you exporting the handler func as default? Default exports in API routes are called with the class `(req: IncomingMessage, res: ServerResponse)` style, but Hono expects a `Request` object so you should use the http method syntax shown in this example. #L12-L16" target="_blank" rel="nofollow noopener">github.com/vercel/hono-st…

I've now managed to get a proper deployment with Vite + Hono, the routing works but now the Auth flow hangs and timesout for no good reason waiting to parse the request json. it's just waiting for c.req.json (and only happens when deployed, locally it does not hang). Deploying this is proven to be preeeety hard haha. Maybe I should stick to the default libs and whatnot. I just wanted to stick to hono which is what I use the most for backend on side-projects.

@ctatedev @cramforce how to best reconcile the OAuth routes for the MCP flows and have it working with NextJS routes? I've created my server without using the standard MCP integration (vercel.com/docs/mcp). So I keep being 'blocked' by the auth flow since the standard routes for OAuth seem to ignore the /api/ entry 🤔

Haven’t had this much camera time since my track days. If you’re a developer looking for a CMS, check it out!

We're excited to share that TInaCMS' Visual Editing just got a major upgrade with the new "Click To Edit" behaviour! 🚀 This pops open the Tina sidebar at the right location when you click editable elements on the page. See how it works in the thread below 🧵 1/6

We’re excited to announce that TinaCMS has gone 1.0! 🚀🎉 tina.io/blog/tina-1-0-…

@dan_abramov TinaCMS sends the tree so it doesn’t support import statements, this avoids any client side eval. You provide your components at render time tina.io/docs/editing/m…. Most of the logic for that is in this package @tinacms/mdx" target="_blank" rel="nofollow noopener">github.com/tinacms/tinacm…

@ddritzenhein Thanks Derek!

Happy B-Day to my buddy @jeffsee_

We just released Read-only Tokens -Runtime server-side logic - Incremental SSG and Server components - Client-side data fetching (CRA included) -Future support for server-side frameworks like @remix_run Check it out 👇 tina.io/docs/graphql/r…

Tina is just getting started, so what does 2022 look like? - More frameworks - Headless API - New UI and so much more @scottgallant talks through the future of Tina and what to expect. tina.io/blog/tinacms-2…

Syntax highlighting is essential for any developer blog. Check out our latest post from @jamesperkins where he walks you through adding it to a Tina powered blog. tina.io/blog/syntax-hi…

Welcome to the future of MDX! Tina is introducing a UI for MDX, giving the power back to your content creators. youtu.be/yYysK7rCNM4

Want to learn more about @tina_cms ? I sat down with @bdougieYO and talked about Tina! In the sit down we: - Demo'd Tina - Talked about adding Tina to your own site - How to help the Open Source project Head over to the @github YouTube Channel to enjoy bit.ly/2Z5qCrA

We are looking for some developers to give feedback on MDX support for @tina_cms. What we are looking for people to: - Deep dive on the feature (don't be scared to break it) - 30 min chat afterwards. DM me if you are interested! A quick preview of how MDX components at work

@tina_cms Also thanks to @yarnpkg for PnP which is how the whole thing hangs together 🙏

Kudos to @jeffsee_ for orchestrating the move. If you're curious here's how it feels in development: loom.com/share/5c6b13ac…

Switching to @vite_js and esbuild is such a productivity boost when developing @typescript packages for @tina_cms. We're up to 11 times faster now 🚀 Thank you so much @evanyou and @evanwallace for providing such great tools 🙏

@DiarioOle twitch.tv/whizzyam

You are customer-focused? You like developing with TypeScript, React, and the latest JS tooling? We're hiring a senior web developer, come and join our team to help us build the future of content management. forestry.io/job-openings/w…