Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
Recent PRs & issues
Summary Fixes #169. When importing , TypeScript fails to resolve module declarations under TypeScript 4.7+ / 5.x resolution modes (, , or ): Root Cause 1. In , only was provided, omitting the export condition. TypeScript requires the condition to be listed first for subpath imports. 2. In , entries existed for , , , , , , and , but was missing. 3. Other subpath export conditions (, , , , ) were also missing explicit conditions in , relying solely on fallback . Changes Added to . Added to . Added explicit conditions across all subpath export targets in . Verification Tested with and in : imports and resolves cleanly without type errors. Verified all existing vitest tests in pass (10/10 test files, 107/107 tests passing). Verified Biome checks pass with zero errors.
Problem SvelteKit 3 removed the module. imported from it and called , which throws at runtime: This crashes hydration for any SvelteKit 3 app using . Fix Use from to observe completed navigations without patching the global History API Keep the existing entry and update to Register from a component initialization, as required by SvelteKit's lifecycle API Update the SvelteKit demo and README to use is available in SvelteKit 2.12 and 3. Its callback receives the completed destination, so page views use the final values. Notes is still used for ; it is deprecated in SvelteKit 3 but not removed until SvelteKit 4 Consumers should call during component initialization, for example from
Recent fixes
🖖 What's in there? Part 4 of EXP-3628: Web Analytics events get their timestamp at ingestion time, not from the client. The server-side , , and functions stop sending . Vercel's ingestion service sets the timestamp when it receives the event. 🤺 How to test? : the request body checks in no longer expect . 🔬 Notes to reviewers ⚠️ Merge after vercel/api#98450 is deployed. The ingestion service requires on the current production version, so it would reject these requests with 400. Older versions of the package still send . The ingestion service accepts it and ignores it. 🔗 Related PRs All PRs are independent (not stacked). Deploy them in this order: 1. vercel/api#98449: the subscriber reads the SNS attribute. 2. vercel/api#98450: ingestion sends and ignores client . 3. vercel/front#90985: the injected script stops sending . 4. This PR: server-side functions stop sending .
🖖 What's in there? Test PR. Do not merge. It adds a 🦆 to the SvelteKit demo home page. It checks that still makes preview deployments after its transfer from to . 🤺 How to test? Make sure the Vercel bot posts a preview for under the team. 🔬 Notes to reviewers Part of EXP-3498. I will close this PR after the check.
Replaces the import in with . was deprecated in SvelteKit 3 in favor of and is scheduled for removal in SvelteKit 4: https://svelte.dev/docs/kit/$app-environment Migrating now avoids a deprecation warning for SvelteKit 3 users and a breaking import when v4 lands (though it's already breaking my prod build). New module reference: https://svelte.dev/docs/kit/$app-env Changes : import from instead of Compatibility note This package still supports SvelteKit 2, where may not exist. I'd appreciate guidance on whether to bump the peer range, wait, or support both. Related I also sent feedback through the docs page, which shows the same outdated import.
Repository: vercel/analytics. Description: Privacy-friendly, real-time traffic insights Stars: 517, Forks: 55. Primary language: TypeScript. Languages: TypeScript (80.9%), Vue (7.2%), CSS (6.5%), Astro (2.6%), JavaScript (1.9%). License: MIT. Homepage: https://vercel.com/analytics Latest release: v2.0.1 (7mo ago). Open PRs: 7, open issues: 27. Last activity: 4d ago. Community health: 50%. Top contributors: tobiaslins, feugy, timolins, dglsparsons, chriswdmr, AndyBitz, atinux, emspishak, Ethan-Arrowood, CHC383 and others.