fix: fix types for custom providers shadowing builtins

[dreitzner]

fix correct type generation for custom providers with same name as built in providers

🔗 Linked issue

resolves #2015

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ 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

This fixes the ttype generation for cases where custom providers have the same name as built in providers.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/image@2016

commit: cad2396

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 6.99%. Comparing base (aba9b7f) to head (cad2396).

Files with missing lines	Patch %	Lines
src/provider.ts	0.00%	6 Missing ⚠️
src/module.ts	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##            main   #2016      +/-   ##
========================================
- Coverage   7.00%   6.99%   -0.01%     
========================================
  Files         78      78              
  Lines       3625    3629       +4     
  Branches     140     140              
========================================
  Hits         254     254              
- Misses      3322    3326       +4     
  Partials      49      49              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[danielroe]

I wonder if we can resolve this with type safety by telling custom provider authors how to augment these interfaces

[dreitzner]

I wonder if we can resolve this with type safety by telling custom provider authors how to augment these interfaces

Not sure how I would implement that 😁

[danielroe]

pushed a change - does this work in your use case?

[dreitzner]

pushed a change - does this work in your use case?

@danielroe yes that works and those changes look a little cleaner than mine 👍

Thank you