npm安装自定义包jest-preset-spfx时嵌套依赖未按指定版本安装问题求助

Let's break down the possible causes and actionable troubleshooting steps to fix the unexpected dependency behavior you're seeing:

1. First, Verify Nested Dependency Installation for @types/jest #

NPM uses a flat dependency tree by default, but when there's a version conflict (like your project having @types/jest@25.2.1 while your package requires 28.1.4), NPM should install the required version inside your package's nested node_modules directory, not the top-level one.

Check if node_modules/jest-preset-spfx/node_modules/@types/jest exists and has version 28.1.4. If it does, this is actually expected behavior—your package will still resolve the correct version locally, even if the top-level has an older one. The confusion might just be from checking only the top-level node_modules.

2. Diagnose ts-jest's Missing Installation via Peer Dependencies #

ts-jest has strict peer dependency requirements for specific versions of Jest and TypeScript. For v28.0.5, run this command to check its peer dependencies:

npm show ts-jest@28.0.5 peerDependencies

Then verify your project's versions of these required peers:

npm list jest
npm list typescript

If your project's versions fall outside ts-jest's required range, NPM 8 might silently skip installing ts-jest (even though it should warn about peer conflicts—double-check your full verbose logs for mentions of "peer dependency" related to ts-jest).

For this case, you should update your package's package.json to declare these peer dependencies explicitly, with version ranges that match ts-jest's requirements. You can use peerDependenciesMeta to mark them as optional if you want to avoid forcing users to install specific versions, but this makes your package's behavior clearer.

3. Rule Out npm-shrinkwrap.json Conflicts #

Your package's shrinkwrap file locks dependencies to specific versions, but when installed in another project, NPM has to reconcile this with the project's existing lock file or dependency tree.

Try temporarily removing the npm-shrinkwrap.json from your package, publish a test version, and install it in your target project. If all dependencies install correctly, the shrinkwrap file was likely causing conflicts. Regenerate it in a clean environment (delete node_modules and package-lock.json first, run npm install, then npm shrinkwrap) to ensure it's compatible with broader installations.

4. Dig Deeper into Verbose Installation Logs #

The audit logs you shared only show version candidates—look through the full npm install --verbose output for ts-jest specifically. Search for lines like:

• skipping ts-jest@28.0.5 because peer dependency jest@x.x.x is not satisfied
• conflicting versions for ts-jest, selecting x.x.x instead of 28.0.5

These lines will give direct clues about why ts-jest isn't installing.

5. Test in a Clean, Isolated Project #

Create a brand-new test project to eliminate conflicts from your existing project's dependencies:

mkdir test-spfx-preset && cd test-spfx-preset
npm init -y
npm install your-jest-preset-spfx-package

If all dependencies install correctly here, the issue is tied to your original project's specific dependency tree. If not, the problem is in your package's configuration (dependencies declaration, shrinkwrap, etc.).

内容的提问来源于stack exchange，提问作者Andrew Connell