You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our rules for loading files from wildcard matches prioritize .d.ts files over .json files (and at the same priority as .js files). Now that we support declaration files for .json and .js files, this is undesirable, as when declarations are emitted in-place (ie, with emitDeclarationsOnly), subsequent compilations using wildcard lookups will load the generated declaration files over the original source .js (maybe) and .json (definitely) files. Fixing this would require rejiggering the extension priority machinery in src\compiler\utilities.ts, so that declaration files are truly the lowest priority extension to load. This comment thread has a bit more discussion on the topic. A cursory glance also leads me to believe that extension priorities for extraFileExtensions as passed into getSupportedExtensions are largely unhandled, so there's probably a fair chunk of work here to revisit this system.
In the meantime, if you encounter an issue likely caused by this discrepancy, the workaround is pretty simple: Use the outDir compiler option.
The text was updated successfully, but these errors were encountered:
Our rules for loading files from wildcard matches prioritize
.d.ts
files over.json
files (and at the same priority as.js
files). Now that we support declaration files for.json
and.js
files, this is undesirable, as when declarations are emitted in-place (ie, withemitDeclarationsOnly
), subsequent compilations using wildcard lookups will load the generated declaration files over the original source.js
(maybe) and.json
(definitely) files. Fixing this would require rejiggering the extension priority machinery insrc\compiler\utilities.ts
, so that declaration files are truly the lowest priority extension to load. This comment thread has a bit more discussion on the topic. A cursory glance also leads me to believe that extension priorities forextraFileExtensions
as passed intogetSupportedExtensions
are largely unhandled, so there's probably a fair chunk of work here to revisit this system.In the meantime, if you encounter an issue likely caused by this discrepancy, the workaround is pretty simple: Use the
outDir
compiler option.The text was updated successfully, but these errors were encountered: