TypeScript Version: 4.0.5
Search Terms: typeAcquisition exclude
Code

Use the following jsconfig.json file:

{
    "compilerOptions": {
        "checkJs": true,
        "strict": true,
        "resolveJsonModule": true,
    },
    "include":[
        "./**/*",
    ],
    "typeAcquisition": {
        "exclude": [
            "copy-webpack-plugin"
        ]
    }
}

Expected behavior:

When identifying that the source of a type-related issue exists in the automatically acquired type declarations, it is natural to add that package to the typeAcquisition.exclude array in the [j/t]sconfig.json file.
Once this is done, the TypeScript language service should not use automatically acquired type declarations for the specified package (the copy-webpack-plugin package in the example above).
In other words, a user should be able to make the configuration adjustment, restart the TypeScript/JavaScript Language Service and find that any packages newly added to the "typeAcquisition.excluded" array should no longer use automatically acquired packages.

Actual behavior:

The TypeScript language service continues to use automatically acquired type declarations for the newly excluded package.
To be clear, in the example above, setting typeAcquisition.enable = falsedoes disable the type acquisition for copy-webpack-plugin .
Manually "uninstalling" the type declarations (using, for example, npm uninstall --save-dev @types/copy-webpack-plugin ) allowed the typeAcquisition.exclude setting to work as expected. In my case, the cache in question was located at ~/.cache/typescript/4.0 .

Playground Link:
N/A. The Playground does not have an option to configure the typeAcquisition setting.
Related Issues:

Couldn't find any.