devtools 0.1.0

Install

Minor changes

The SDK now reports what it is doing in development, so the new @cookieyes/devtools panel can show it. Production builds are unchanged.

What is reported. Consent saves, integration status changes, requests the network blocker stops, Google Consent Mode updates, the region decision, and every script or iframe the SDK manages (registerScript, GatedScript, GatedFrame and the @cookieyes/scripts integrations). The reports go onto a global array that the panel reads, the same way a page reads window.dataLayer. Every report is guarded by process.env.NODE_ENV, so a production build removes it.

New: force a region in development. resolveRegion() takes an optional third argument, a region code to use instead of detection, and RegionDecision.source can now be "forced". Without the argument it behaves exactly as before. CookieYesProvider accepts a forcedRegion prop, and @cookieyes/nextjs/server adds getServerRegion(). It returns the region from the request's geo headers, the header that supplied it, the GPC signal and any devtools override, so a server-rendered banner follows a forced region. Production builds ignore overrides.

In @cookieyes/core, @cookieyes/nextjs, @cookieyes/react, @cookieyes/scripts.

New package: @cookieyes/devtools, a panel for your dev server that shows what the SDK is doing and lets you test it.

import { CookieYesDevtools } from "@cookieyes/devtools";
import "@cookieyes/devtools/styles.css";

<CookieYesDevtools />;

See what the SDK is doing. Saved and unsaved consent side by side, integration statuses, blocked requests, Google Consent Mode signals, and a searchable timeline of events that survives a reload. Open the preferences or opt-out dialog, reset consent, or download a debug file for a bug report.

Test without a VPN. Force any country or US state and see the regulation it gets, and switch the banner's language live.

Find scripts that load without consent. The Scanner lists third-party scripts, iframes, requests, cookies and localStorage keys, shows which ones the SDK manages, and flags anything that appeared before its category was granted or after it was withdrawn. Each unmanaged one comes with the code that would gate it.

Nothing reaches production. A production build resolves an empty component and an empty stylesheet, so you can leave both imports in place. Install it as a dev dependency; it needs no flag. React and Next.js only for now, and it needs the @cookieyes/core and @cookieyes/react released alongside it.

In @cookieyes/devtools.

Patch changes

The README on npm now opens with the CookieYes banner, like the other packages.

Documentation only; no behaviour change.

In @cookieyes/scripts, @cookieyes/test.

Source