Search Results for "browser dev"

...View fired mutations, and variables, and re-run individual mutations. Visualize the Apollo Client cache and search through it by field names and/or values. You can install the extension via Firefox Browser Add-ons or the Chrome Webstore. If you want to install a local version of the extension instead, skip ahead to the Developing section. While your application is in dev mode, the devtools will appear as an "Apollo" tab in your web browser inspector.

...Instead of juggling multiple CLIs and scattered logs, it gives you a unified UI for common Cloudflare primitives like D1 databases, KV namespaces, R2 buckets, Durable Objects, and Queues. The D1 experience is more than a viewer: it includes a SQL editor and a data browser with inline editing, filtering, sorting, bulk operations, and even dummy data generation so you can iterate quickly. For KV and R2 it provides practical file-and-record management, letting you view, update, delete, upload, and download as part of your normal dev loop. It also includes tools for testing queue behavior by sending messages and inspecting results, which helps validate event-driven logic without deploying.

...Share components with your team, including designers and developers. See how components react to different props and data right in the browser. Find the right combination of props and copy the code.

Stencil is a toolchain for building reusable, scalable design systems. Generate small, blazing fast, and 100% standards based Web Components that run in every browser. The magical, reusable web component compiler. Start building in seconds. With intentionally small tooling, a tiny API, and zero configuration, Stencil gets out of the way and lets you focus on your work. A tiny runtime, prerendering, and the raw power of native Web Components make Stencil one of the fastest compilers around....

patch-package lets app authors instantly make and keep fixes to npm dependencies. It's a vital band-aid for those of us living on the bleeding edge. Patches created by patch-package are automatically and gracefully applied when you use npm(>=5) or yarn. No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working. You can use --save-dev if you don't need to run npm in production, e.g. if you're...