TypeScript Configuration Prevents Proper Module System Usage in Boilerplate project template

[ysmoradi]

The TypeScript configuration in Boilerplate.Client.Core currently lacks proper module system setup, which creates several issues:

1. Missing Module Output Configuration: The tsconfig.json previously used outFile to compile all TypeScript into a single app.js, but there's no proper module system configured to support modern ES module imports/exports.
2. Scattered Type Declarations: TypeScript type definitions for external libraries (Blazor, Bit.Butil, Bit.BlazorUI) are currently declared inline within individual script files rather than in a centralized location, leading to:
   • Code duplication across multiple files
   • Inconsistent type declarations
3. No Entry Point Module: There's no clear entry point that coordinates the import and initialization of all application scripts, making it unclear how different modules relate to each other and in what order they should execute.
4. Missing Module Resolution Strategy: Without explicit module and moduleResolution settings, TypeScript cannot properly resolve imports between files, leading to potential build issues and IDE confusion.
   Impact
   • Developers cannot reliably use import/export statements between TypeScript files
   • Build process lacks clarity about how TypeScript files are transformed and bundled

[github-actions]

Hello there! I'm a wiki 🤖.

Based on the content of this thread, I've found a potentially relevant wiki page for you!

✨ View Wiki Page

I hope this helps!