analytics-next
analytics-next copied to clipboard
Segment Analytics.js 2.0
- only redact 'target.value' in `interaction` signals - do not redact instrumentation signals
- [ ] I've included a changeset (psst. run `yarn changeset`. Read about changesets [here](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md)).
- [ ] I've included a changeset (psst. run `yarn changeset`. Read about changesets [here](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md)).
Bumps [next](https://github.com/vercel/next.js) from 12.3.4 to 14.2.10. Release notes Sourced from next's releases. v14.2.10 [!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary. Core...
Did you consider adding support for the Beacon API as a "transport layer" alternative to `fetch`/`XHR`? This native API is created with analytics in mind and helps increasing reliability of...
Bumps [webpack](https://github.com/webpack/webpack) from 5.76.1 to 5.94.0. Release notes Sourced from webpack's releases. v5.94.0 Bug Fixes Added runtime condition for harmony reexport checked Handle properly data/http/https protocols in source maps Make...
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 2.9.18 to 3.2.11. Changelog Sourced from vite's changelog. 3.2.11 (2024-09-17) fix: backport #18112, fs raw query (a6da450), closes #18112 fix: backport #18115, DOM Clobbering in (2ddd854), closes...
`analytics.ready(() =>` waits for _all_ destinations to be loaded which is a bit slow. When you just need the current (initial) user, you can use 'initialize' instead. Needed for the...