docs(nuxt): fix file path for file router

[th1m0]

Changed the file path for the file router to match Nuxt's structure.

Summary by CodeRabbit

• Documentation
  • Updated Nuxt module setup guide with simplified file path for uploadthing.ts
  • Added compatibility date configuration for Nuxt project

[changeset-bot]

⚠️ No Changeset found

Latest commit: bcfe1e5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-uploadthing	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 4, 2025 9:34pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
legacy-docs-uploadthing	⬜️ Ignored (Inspect)	Visit Preview		Jan 4, 2025 9:34pm

[coderabbitai]

Walkthrough

The pull request introduces two primary changes: an update to the UploadThing Nuxt module documentation by modifying the file path reference, and a configuration adjustment in the Nuxt playground's configuration file. The documentation change simplifies the path for the uploadthing.ts file, while the Nuxt configuration adds a compatibility date to ensure proper module interaction.

Changes

File	Change Summary
docs/src/app/(docs)/getting-started/nuxt/page.mdx	Updated file path from src/lib/server/uploadthing.ts to server/uploadthing.ts
packages/nuxt/playground/nuxt.config.ts	Added compatibilityDate: "2024-04-03" to the configuration

Possibly related PRs

• fix(docs): force path resolution #953: Path resolution updates for UploadThing library
• docs: Add getting started for tanstack/start #973: Getting started guide for Tanstack/Start with file routing and upload functionality
• docs: Fixed SolidStart and slightly changed Tanstack/Start #988: Documentation modifications for Tanstack/Start, including file routing updates
• fix: nuxt module tailwind support #1033: Nuxt module compatibility enhancements with Tailwind CSS
• fix: nuxt module options #1056: Nuxt module options and environment variable improvements
• fix: call use client properly #1053: Documentation update for Next.js App Router with UploadThing

Suggested reviewers

• juliusmarminge

---

📜 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 68c261f and bcfe1e5.

📒 Files selected for processing (2)

• docs/src/app/(docs)/getting-started/nuxt/page.mdx (1 hunks)
• packages/nuxt/playground/nuxt.config.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• docs/src/app/(docs)/getting-started/nuxt/page.mdx

🔇 Additional comments (1)

packages/nuxt/playground/nuxt.config.ts (1)

6-6: Validate and confirm your compatibility date.

The added compatibilityDate property looks fine at first glance. However, Nuxt or associated modules might expect changes or behaviors aligned with specific versions. Double-check any relevant release notes or migration docs to ensure that using "2024-04-03" aligns with the intended features and isn't out of sync with more recent instrumentation.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[th1m0]

Not sure if a changeset is needed for docs update

[markflorkowski]

this seems fine to me, how did you choose the compatability date?

[th1m0]

It's the date this was added; however, today's date will also work fine if you prefer. It doesn't serve any real purpose here, but if you leave it out, you'll keep being prompted to add it. This only matters if you deploy this somewhere, which isn't the case here.