如何忽略非直接依赖包globby的类型声明文件错误？

Hey fellow dev, I feel your pain—dealing with type errors from a dependency you didn't even install directly is super frustrating. Let's go through a few solid ways to fix those globby type declaration errors you're seeing:

1. Skip All Third-Party Library Type Checks (Recommended) #

The easiest and most effective fix for this scenario is to tell TypeScript to skip validating type declarations from all node_modules packages. Just add the skipLibCheck option to your tsconfig.json:

{
  "compilerOptions": {
    "skipLibCheck": true,
    // Keep all your existing compiler options here
  },
  // ... other configs
}

This will ignore all type errors from external libraries while keeping full type checking for your own code—perfect for when you don't care about fixing someone else's broken types.

2. Exclude Only globby's Type File #

If you don't want to skip checks for all libraries, you can specifically exclude globby's problematic type declaration file in tsconfig.json:

{
  "exclude": [
    "node_modules/globby/index.d.ts",
    // Any other files you need to exclude
  ]
}

Note: This might cause issues if another dependency in your project relies on globby's types—you might get "type not found" errors in that case.

3. Use @ts-ignore for Local Fixes #

If only a few files in your codebase are triggering these errors, you can add a // @ts-ignore comment above the line that's importing or using globby-related types:

// @ts-ignore
import { GlobbyOptions } from 'globby';

// Or if it's a usage line:
// @ts-ignore
const options: GlobbyOptions = { /* ... */ };

This is a quick band-aid, but avoid overusing it—it can hide real type issues in your own code.

4. Upgrade Your TypeScript Version #

Looking at the error messages (like the readonly string[] syntax issues), it seems your TypeScript version might be outdated. The readonly array modifier was introduced in TypeScript 3.4, so upgrading to a newer version might resolve these syntax errors entirely:

# Using npm
npm install typescript@latest --save-dev

# Using yarn
yarn add typescript@latest --dev

Just be aware that upgrading TS might introduce other compatibility issues with your project, so give it a quick test after updating.

Why This Happens #

Those errors are likely because globby's type declarations use TypeScript features that your current version doesn't support, or the type file got corrupted during installation. Either way, the solutions above should get you back up and running quickly.

内容的提问来源于stack exchange，提问作者Faisal Manzer