Updates jsconfig generator to add settings
What does this MR do and why?
Adds typeAcquisition
entry to enforce Type Acquisition and several compilerOptions
to improve performance and interoperability with some of our npm modules and json file imports.
"typeAcquisition": {
"enable": true
},
"compilerOptions": {
"skipLibCheck": true,
"resolveJsonModule": true,
// ...
},
edit: "esModuleInterop" was dropped, see !130116 (comment 1533841541).
Screenshots or screen recordings
VSCode JSON import example for ee/spec/frontend/usage_quotas/storage/mock_data.js
:
JSON before | JSON after |
---|---|
![]() |
![]() |
![]() |
![]() |
Webstorm was already handling JSON files (more or less fine), nothing changed for Webstorm.
How to set up and validate locally
To regenerate a jsconfig.json
file, run node ./scripts/frontend/create_jsconfig.js
from GitLab project root.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Kos Palchyk