feat: extend generated tsconfig paths from aliases

[gioboa]

🔗 Linked issue

Fixes: #2476

❓ 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

To manage aliases inside the configuration and create the correct tsconfig file I merged the alias object with the typescript one ( that already works )
To prevent errors we need to check the complex typescript object 😭
I added typeof checks to prevent errors with wrong configs like eg. alias: 0 or paths: true

export default defineNitroConfig({
  alias: {  👈 the PR manage this config
    foo: fileURLToPath(new URL("../bar", import.meta.url)),   
  },
  typescript: {
    strict: true,
    tsConfig: {
      files: [],
      compilerOptions: {
        allowJs: true,
        paths: {
          baz: [ fileURLToPath(new URL("../bar", import.meta.url)) ]
        }
      }
    }
  },
});

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[gioboa]

Do I need to do the same change to v3?

[pi0]

It will be ported to v3 branch. i need to test it little bit to merge for next minor (after patch)

[productdevbook]

#3056

Thank you, it’s working great! However, the order needed to be adjusted, and the structure had to be improved. You can check out the new PR now.

[gioboa]

Do I need to close this one?

[productdevbook]

Do I need to close this one?

No, @pi0 will decide after examining it.