Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(nuxt): remove misleading .ts for resolve #25855

Merged
merged 1 commit into from Feb 19, 2024
Merged

Conversation

manniL
Copy link
Member

@manniL manniL commented Feb 19, 2024

πŸ”— Linked issue

#20998

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

From Daniel's comment:

You should not add the .ts extension as this will not be present when you build your module.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have added tests (if possible).
  • I have updated the documentation accordingly.

Copy link

stackblitz bot commented Feb 19, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

nuxt-studio bot commented Feb 19, 2024

βœ… Live Preview ready!

Name Edit Preview Latest Commit
Nuxt Docs Edit on Studio β†—οΈŽ View Live Preview b48ee47

@manniL manniL changed the title docs(modules): remove misleading .ts for resolve docs(nuxt): remove misleading .ts for resolve Feb 19, 2024
Copy link
Member

@huang-julien huang-julien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I sometimes still make that mistake πŸ˜‚

@manniL
Copy link
Member Author

manniL commented Feb 19, 2024

I sometimes still make that mistake πŸ˜‚

Might be a good ESLint rule then? πŸ€”
Or a dev warning in resolve?

@danielroe danielroe merged commit 9326b7a into main Feb 19, 2024
4 of 7 checks passed
@danielroe danielroe deleted the manniL-patch-1 branch February 19, 2024 10:36
@github-actions github-actions bot mentioned this pull request Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants