Avoid installing @types typings in dependencies

Question

Avoid installing @types typings in dependencies

Can I prevent global typings from being included in installed dependencies?

I recently installed a local dependency, which led to the node_modules folder of that dependency being copied over. Within this node_modules folder are @types typings that clash with those already installed for the main project.

For example,

project-path/node_modules/local-dependency/node_modules/@types/react

conflicts with

project-path/node_modules/@types/react

.

Is there a way to instruct the TypeScript compiler to disregard the typings within that local dependency?

typescript typescript-typings

Answer 1

Answer №1

Another option is to include "skipLibCheck": true in the compiler settings.

Answer 2

Another option is to include "skipLibCheck": true in the compiler settings.

Answer 3

Answer №2

Have you attempted to utilize an empty array in the types option?

{
  "compilerOptions": {
    ...,
    "types": []
  }
}

This will deactivate the automatic inclusion of types.

For further information, please refer to the TypeScript documentation.

Answer 4

Have you attempted to utilize an empty array in the types option?

{
  "compilerOptions": {
    ...,
    "types": []
  }
}

This will deactivate the automatic inclusion of types.

For further information, please refer to the TypeScript documentation.

Answer 5

Answer №3

One way to have more control over which files the TypeScript compiler includes is by using the include and exclude properties in your tsconfig.json file:

Check out this link for more information.

The "include" and "exclude"properties allow you to specify glob-like file patterns. You can use wildcards like * to match characters, ? to match any one character, and **/ to recursively match subdirectories.

You can customize your configuration further by specifying specific exclusions, such as excluding the node_modules directory:

{

    ...    

    "exclude": [
        "node_modules"
    ]
}

If needed, you can create a targeted glob pattern to exclude only the problematic dependencies, like node_modules, while still including other necessary files.

If you're facing conflicts with different versions of modules, consider updating your dependencies or app to ensure they both use the same version. This may require deleting existing npm modules and performing a fresh npm install to resolve conflicts and ensure a shared module version.

Answer 6

One way to have more control over which files the TypeScript compiler includes is by using the include and exclude properties in your tsconfig.json file:

Check out this link for more information.

The "include" and "exclude"properties allow you to specify glob-like file patterns. You can use wildcards like * to match characters, ? to match any one character, and **/ to recursively match subdirectories.

You can customize your configuration further by specifying specific exclusions, such as excluding the node_modules directory:

{

    ...    

    "exclude": [
        "node_modules"
    ]
}

If needed, you can create a targeted glob pattern to exclude only the problematic dependencies, like node_modules, while still including other necessary files.

If you're facing conflicts with different versions of modules, consider updating your dependencies or app to ensure they both use the same version. This may require deleting existing npm modules and performing a fresh npm install to resolve conflicts and ensure a shared module version.

Avoid installing @types typings in dependencies

Answer №1

Answer №2

Answer №3

Similar questions

"Enhancing user experience with MaterialUI Rating feature combined with TextField bordered outline for effortless input

typescript in conjunction with nested destructuring

Is there a way to resolve the issue of retrieving the processed value directly in NestJS's @OnEvent function?

Sorting functionality is functional, but the table content remains unsorted within the Angular Material Table

Creating TypeScript declaration file for exporting JavaScript function

Is there a way to logout when the select event occurs using the key?

An unexpected error has occurred: Uncaught promise rejection with the following message: Assertion error detected - The type provided is not a ComponentType and does not contain the 'ɵcmp' property

At what point does the constructor of an injected service in Angular execute?

Typescript: The argument provided, which is of type 'number', cannot be matched to a parameter of type 'string'

Unable to retrieve props from server-side page to client-side component in a Next.js application router

Is there an issue with the newline character ` ` not functioning properly in TypeScript when used with the `<br/>` tag?

Guide to initializing the state in pinia with Typescript

Inputting Dates Manually in the Angular Material Datepicker Field

What is the reason behind the file not found error encountered when running Deno with the command "echo hello"?

What is the most effective way to move specific data from one page to another in Angular/Typescript?

Tips for integrating error management in Angular with RXJS

Why is it that retrieving the same class data from two separate TypeScript files yields varying results in TypeScript? What steps can be taken to resolve this issue

Exploring the use of Observables in Angular 2 services

Utilize TypeScript to narrow down function parameters within a callback by evaluating other parameters

TypeScript infers the return type by analyzing the callback property of an object parameter