chore: update docs

[jill64]

Summary by CodeRabbit

• Documentation

  • Updated the README.md to reflect changes in error handling setup for Sentry integration in a SvelteKit Cloudflare application.

• Refactor

  • Renamed and updated import statements for Sentry initialization in both client and server-side hooks.
  • Adjusted function calls to align with the new import paths and Sentry setup procedures.

[coderabbitai]

Warning

Rate Limit Exceeded

@jill64 has exceeded the limit for the number of files or commits that can be reviewed per hour. Please wait 5 minutes and 40 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 63e3340 and b9d57ca.

Walkthrough

The update involves a refactor of Sentry integration in a SvelteKit Cloudflare application. The clientInit and serverInit functions from the @jill64/sentry-sveltekit-cloudflare package have been renamed to a unified init function, now imported from separate client and server paths. This change simplifies the import process and potentially aligns with Sentry's updated API or the package's new structure.

Changes

File Path	Change Summary
hooks.client.js	Renamed clientInit to init from .../sentry-sveltekit-cloudflare/client
hooks.server.js	Renamed serverInit to init from .../sentry-sveltekit-cloudflare/server

🐇✨
In the code where errors are caught,
A rabbit hopped and a change it brought.
From clientInit to init it leapt,
In Sentry's embrace, all exceptions are kept. 🌟🐾

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	5644810
Status:	✅  Deploy successful!
Preview URL:	https://f22a4656.sentry-sveltekit-cloudflare.pages.dev
Branch Preview URL:	https://dev.sentry-sveltekit-cloudflare.pages.dev

View logs

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 370a124 and 63e3340.

Files selected for processing (1)

• README.md (2 hunks)

Additional comments: 3

README.md (3)

• 37-45: The documentation correctly reflects the updated import path and function name for client-side Sentry initialization. The commented-out alternative import statement provides clarity for users migrating from the old setup.

• 61-69: The documentation correctly reflects the updated import path and function name for server-side Sentry initialization. The commented-out alternative import statement is helpful for users transitioning from the previous configuration.

• 35-45: > Note: This review was outside the patches, so it was mapped to the patch with the greatest overlap. Original lines [35-69]

The README.md updates are consistent with the PR objectives and AI-generated summaries, providing clear guidance on the new Sentry integration setup for both client and server sides.