fix: update insight script

[andostronaut]

This is an automated pull request for branch fix/update-pkg-name

Summary by CodeRabbit

• Chores
  • Updated the project’s identifier to reflect its new scoped namespace.
  • Adjusted the homepage’s tracking mechanism by changing the analytics script source and identifier.

[coderabbitai]

Walkthrough

This pull request makes two configuration updates. In the package.json file, the package name is changed from "docs" to "@kinotiodotio/docs", introducing a scoped namespace. In the src/pages/index.tsx file, the <Script> component is modified to use a new source URL and website identifier for analytics. No other changes or functional updates are included.

Changes

File	Change Summary
package.json	Updated the package name from "docs" to "@kinotiodotio/docs".
src/pages/index.tsx	Changed the <Script> source URL from https://umami.kinotio.io/script.js to https://insight.kinotio.io/script.js and updated the data-website-id.

Poem

I'm a hare with a joyful beat,
Hopping through code with little feet.
Package names now scoped with flair,
And analytics scripts soar through the air.
In every update, a carrot of delight—
Coding with joy, from morning to night!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2cfdbe6 and e818e27.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/pages/index.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build (20)
• GitHub Check: build (20)

🔇 Additional comments (2)

package.json (1)

2-2: Package name updated to use organization scope.

The package name has been changed from "docs" to "@kinotiodotio/docs", introducing a proper namespace scope. This follows npm package naming best practices for organizing related packages.

src/pages/index.tsx (1)

73-74:

✅ Verification successful

Analytics script source and website ID updated.

The analytics script is now pointing to a new endpoint at "insight.kinotio.io" (previously "umami.kinotio.io") with a new website identifier. This appears to be a migration to a different analytics tracking configuration.

---

🏁 Script executed:

#!/bin/bash
# Verify the new analytics endpoint is accessible
curl -I https://insight.kinotio.io/script.js

Length of output: 1105

---

Action: Verified Updated Analytics Endpoint

The code change in src/pages/index.tsx (lines 73-74) updating the analytics script's source from umami.kinotio.io to insight.kinotio.io with the new website ID (e5e1620a-e7a1-4203-af06-25ed8ea2a97a) has been verified. The curl check successfully returned HTTP/2 200, confirming that the new endpoint is accessible and properly configured.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.