---
title: "#web-apis articles | Hashnode"
description: "Explore 42 articles tagged #web-apis on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/web-apis"
---

Tag

# #web-apis

42 posts · 1 followers

[Dan Holloran](https://hashnode.com/@grimicorn) · [Oct 31](https://hashnode.com/posts/laravel-13-json-api-resources-spec-compliant-responses-without-a-package/6ae5bf84ff2883ccf3a41bbe)

### [Laravel 13 JSON:API Resources: Spec-Compliant Responses Without a Package](https://grimicorn.hashnode.dev/laravel-13-json-api-resources-spec-compliant-responses-without-a-package?utm_source=hashnode&utm_medium=feed)

Every team that builds a JSON API eventually has the same argument. Should relationships be nested or side-loaded? Is the ID a string or an integer? How does the client ask for fewer fields? You can s

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/laravel-13-json-api-resources-spec-compliant-responses-without-a-package?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Oct 27](https://hashnode.com/posts/json-parse-source-text-access-stop-losing-precision-on-big-ids/6ae079a170a3906705961234)

### [JSON.parse Source Text Access: Stop Losing Precision on Big IDs](https://grimicorn.hashnode.dev/json-parse-source-text-access-stop-losing-precision-on-big-ids?utm_source=hashnode&utm_medium=feed)

Your API returns an order ID of 9007199254740993. Your frontend logs 9007199254740992. Nobody touched it. JSON.parse quietly rounded it, because every JSON number becomes a JavaScript double, and doub

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/json-parse-source-text-access-stop-losing-precision-on-big-ids?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Oct 12](https://hashnode.com/posts/css-container-style-queries-let-the-parent-set-the-theme/6accb2d532158f06f0120409)

### [CSS Container Style Queries: Let the Parent Set the Theme](https://grimicorn.hashnode.dev/css-container-style-queries-let-the-parent-set-the-theme?utm_source=hashnode&utm_medium=feed)

Every design system eventually grows a modifier class problem. The card needs a dark version for the footer, a compact version for the sidebar, and a "highlighted" version for the pricing page. So you

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/css-container-style-queries-let-the-parent-set-the-theme?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Oct 5](https://hashnode.com/posts/nuxt-createusefetch-one-typed-api-client-without-the-wrapper-boilerplate/6ac379a762094b0d619ccc5a)

### [Nuxt createUseFetch: One Typed API Client Without the Wrapper Boilerplate](https://grimicorn.hashnode.dev/nuxt-createusefetch-one-typed-api-client-without-the-wrapper-boilerplate?utm_source=hashnode&utm_medium=feed)

Every Nuxt app that talks to a real backend ends up with the same problem. You call useFetch('/users') in one page, then useFetch('/orders') in another, and before long every call site is repeating th

4 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/nuxt-createusefetch-one-typed-api-client-without-the-wrapper-boilerplate?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Sep 28](https://hashnode.com/posts/compression-dictionaries-ship-only-the-diff-when-your-bundle-changes/6aba3e459326c884db645e44)

### [Compression Dictionaries: Ship Only the Diff When Your Bundle Changes](https://grimicorn.hashnode.dev/compression-dictionaries-ship-only-the-diff-when-your-bundle-changes?utm_source=hashnode&utm_medium=feed)

You ship a one-line bug fix. Your bundler dutifully produces app.8f3c1a.js, a brand new filename, and every returning visitor downloads the whole 270 KB file again. The browser already has 99% of thos

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/compression-dictionaries-ship-only-the-diff-when-your-bundle-changes?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Sep 25](https://hashnode.com/posts/uint8array-tobase64-and-tohex-stop-round-tripping-bytes-through-btoa/6ab64a239dc5c4c057be1536)

### [Uint8Array toBase64 and toHex: Stop Round-Tripping Bytes Through btoa](https://grimicorn.hashnode.dev/uint8array-tobase64-and-tohex-stop-round-tripping-bytes-through-btoa?utm_source=hashnode&utm_medium=feed)

Every codebase that touches binary data has the same little helper buried in a utils folder. It takes a Uint8Array, spreads it into String.fromCharCode, hands the result to btoa, and hopes for the bes

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/uint8array-tobase64-and-tohex-stop-round-tripping-bytes-through-btoa?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Sep 15](https://hashnode.com/posts/webnn-the-only-web-api-that-can-reach-your-npu/6aa9198f96cbe75be3f1607d)

### [WebNN: The Only Web API That Can Reach Your NPU](https://grimicorn.hashnode.dev/webnn-the-only-web-api-that-can-reach-your-npu?utm_source=hashnode&utm_medium=feed)

There is a piece of silicon in your laptop that your web app has never once used. If you bought a machine in the last couple of years, it almost certainly has an NPU: a small, power-efficient accelera

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/webnn-the-only-web-api-that-can-reach-your-npu?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Sep 14](https://hashnode.com/posts/graphql-oneof-exactly-one-input-enforced-by-the-schema/6aa7c7e94beab7f912a6a562)

### [GraphQL @oneOf: Exactly One Input, Enforced by the Schema](https://grimicorn.hashnode.dev/graphql-oneof-exactly-one-input-enforced-by-the-schema?utm_source=hashnode&utm_medium=feed)

Every GraphQL schema I've worked on eventually grows a field that can be looked up more than one way. You want a user by ID, or by email, or by username. The type system has no way to say "exactly one

4 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/graphql-oneof-exactly-one-input-enforced-by-the-schema?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Aug 29](https://hashnode.com/posts/the-web-locks-api-one-tab-does-the-work-the-rest-wait/6a9295b1e0bcaf3a26021869)

### [The Web Locks API: One Tab Does the Work, the Rest Wait](https://grimicorn.hashnode.dev/the-web-locks-api-one-tab-does-the-work-the-rest-wait?utm_source=hashnode&utm_medium=feed)

A user opens your dashboard, then opens it again in a second tab, then leaves a third one parked on another monitor from yesterday. Their access token expires. All three tabs notice at roughly the sam

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/the-web-locks-api-one-tab-does-the-work-the-rest-wait?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [Aug 29](https://hashnode.com/posts/form-associated-custom-elements-web-components-that-belong-in-a-form/6a92948f1915d46948182155)

### [Form-Associated Custom Elements: Web Components That Belong in a Form](https://grimicorn.hashnode.dev/form-associated-custom-elements-web-components-that-belong-in-a-form?utm_source=hashnode&utm_medium=feed)

Custom elements have been shippable for years, but the illusion falls apart the moment you drop one inside a <form>. The value never shows up in FormData. required does nothing. Hitting reset leaves y

4 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/form-associated-custom-elements-web-components-that-belong-in-a-form?utm_source=hashnode&utm_medium=feed)
