Skip to content

fix(jsconfig): resolve deprecated baseUrl option warning #924

@beatrizsmerino

Description

@beatrizsmerino

fix(jsconfig): resolve deprecated baseUrl option warning

⏱️ Estimate 📊 Priority 📏 Size 📅 Start 📅 End
1h P0 XS 25-01-2026 25-01-2026

📸 Screenshots

Current Expected
N/A — This change has no visual impact. N/A — This change has no visual impact.

📝 Summary

  • IDE shows deprecation warning for baseUrl option in jsconfig.json
  • The jsconfig.json schema is validated against TypeScript compiler options

💡 Why this bug?

  • Warning message appears in IDE:
Option 'baseUrl' is deprecated and will stop functioning in TypeScript 7.0.
Specify compilerOption '"ignoreDeprecations": "6.0"' to silence this error.
  • baseUrl was originally designed for AMD module loaders in the browser, a use case that is no longer relevant
  • Since TypeScript 4.1, paths works without baseUrl as long as paths use relative prefixes (e.g., "./*")
  • TypeScript 7.0 is being rewritten in Go and will not reimplement baseUrl

Timeline

Version Status
TypeScript 5.x/6.x baseUrl works but shows deprecation warning
TypeScript 7.0 baseUrl will be removed

✅ Expected behavior

  • IDE shows no deprecation warnings
  • Remove baseUrl option since it is no longer required when using paths
  • The current paths already use relative prefixes ("./*") so they work without baseUrl

📋 Steps

Phase 1: Remove deprecated option

  • Remove "baseUrl": "." from compilerOptions in jsconfig.json:
 {
   "compilerOptions": {
-    "baseUrl": ".",
     "paths": {
       "~/*": ["./*"],
       "@/*": ["./*"],
       "~~/*": ["./*"],
       "@@/*": ["./*"]
     }
   }
 }

🧪 Tests

  • IDE shows no deprecation warnings
  • Path aliases still work correctly

🔗 References

Files to modify

  • jsconfig.json

Documentation

Metadata

Metadata

Labels

bugSomething isn't workingconfigurationProject setup and configuration files

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions