GitHub - vercel-labs/emulate: Local API emulation for CI and no-network sandboxesYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
GitHub - bikeshaving/shovel: Run Service Workers anywhere
// server.ts import {Router} from "@b9g/router"; const router = new Router(); router.route("/kv/:key") .get(async (req, ctx) => { const cache = await self.caches.open("kv"); const cached = await cache.match(ctx.params.key); return cached ?? new Response(null, {status: 404}); }) .put(async (req, ctx) => { const cache = await self.caches.open("kv"); await cache.put(ctx.params.key, new Response(await
Introducing Deno Sandbox | Deno
Over the past year, we’ve seen a shift in what Deno Deploy customers are building: platforms where users generate code with LLMs, and that code runs immediately without review. That code frequently calls LLMs itself, which means it needs API keys and network access. This isn’t the traditional “run untrusted plugins” problem. It’s deeper: LLM-generated code, calling external APIs with real credenti
Server-Side WebAssembly - Danilo Chiarlone
Become ISC2 Certified in Cybersecurity—Save 45% TODAY ONLY!
Local Server Security Best Practices
🌐 この記事を日本語で読む A great deal of time and effort is poured into the security of production servers. However, the security of local servers running on developers' machines is often overlooked. In fact, at the beginning of this year, I investigated, reported, and fixed vulnerabilities in several front-end development tools. This article, based on that experience and research, explains specific attack
Pikku - Write Once, Run Everywhere | Pikku
Write Backend Logic Once. Run It Everywhere.Write your backend logic once. Pikku automatically adapts it to work with any protocol—HTTP APIs, WebSockets, queues, scheduled tasks, and even AI tools via MCP. No duplicate code, no vendor lock-in. ✓Unified backend logic across all protocols✓Serverless or server — deploy to any platform without code changes✓Full TypeScript type safety end-to-end✓Produc
@lazarv/react-server
Execute React components across server, client, workers, and edge environments using a single runtime — with React Server Components, streaming, and deployment built in. The Idea React as a RuntimeReact runs outside the browser. Components are executable units — they run on the server, in workers, and at the edge. The runtime decides where and how each component executes. There is no runtime bound
Homepage » Jeasx - JSX with Ease
The Ease of JSX with the power of SSR The developer experience of asynchronous JSX with the proven benefits of server-side rendering, resulting in a robust and streamlined web development approach. export default async function ({ request, reply }) { const id = request.query["id"]; const { name, image, ingredients } = await ( await fetch(`https://dummyjson.com/recipes/${id}`) ).json(); return ( <a
Next.js App Routerの"use server"雑感 : Rails視点から
はじめに Next.jsにServer Actionが新しく導入されました。サーバ上の関数をブラウザから直接呼び出すようなコードの書き味を提供するもので、非常に魅力のあるコンセプトだと私は思っています。ただしサーバ上で実行されるコードとブラウザで実行されるコードの境界が曖昧で、"use server"のセキュリティ上の懸念もよく議論されています。 一方で、私の先日の記事Next.jsで簡単なCRUDアプリを作りながら気になったセキュリティ: Railsの視点からで、私はこの"use server"問題には言及しませんでした。まだ非常に新しい話題でかつNext.js側の対応も進行中だというのもありますが、実は個人的にあまり気にならないのが最大の理由です。 気にならなくなったきっかけは、Server ActionをRuby on Railsのコントローラと同じように考え始めたことです。こうする
Release v5.0.0 · fastify/fastify
What's Changed add missing route shorthands by @Uzlopak in #4409 lib: drop setDefaultRoute and getDefaultRoute methods by @RafaelGSS in #4485 Sync next-branch by @github-actions in #4815 Next: Disallow decorate('name', null) in the types by @voxpelli in #4878 feat!: Add req.hostname and req.port by @aarontravass in #4766 Change request id header default value to false by @philippviereck in #4194 R
Elysia 1.0 - Lament of the Fallen
Elysia 1.0 is the first stable release after development for 1.8 years. Since we started, we have always been waiting for a framework that focuses on developer experience, velocity, and how to make writing code for humans, not a machine. We battle-test Elysia in various situations, simulate medium and large-scale projects, shipping code to clients and this is the first version that we felt confide
Does useQuery run on server-side rendering?
In Next JS: SSR - Server side rendering - getServerSideProps SSG - Static site generated - getStaticPaths & getStaticProps CSR - Client side rendering - everything else It is important to note that SSG functions are run server-side. On the client, you only want to create a single global instance of Apollo Client. Creating multiple instances of Apollo Client will make it challenging to keep things
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
データセンター一覧 - JDCC 日本データセンター協会
GitHub - vercel-labs/portless: Replace port numbers with stable, named .localhost URLs. For humans and agents.
https://www.uber.com/en-AU/blog/ubers-rate-limiting-system/
GitHub - punkpeye/pipenet: Expose your local server to the public internet instantly
GitHub - gaearon/rscexplorer: A tool for people curious about the React Server Components protocol
https://www.npmjs.com/package/@remix-run/node-fetch-server
GitHub - h3js/srvx: λ Universal Server based on web standards.
GitHub - ije/mono-jsx: `<html>` as a `Response`.