Skip to content

Geotiff peer dependency lead to dependency issues #516

@maxnowack

Description

@maxnowack

The geotiff dependency was moved from devDependencies to peerDependencies in #511.
This change breaks the installation of npm dependencies in my project when using npm ci during the Docker build step. The error message correctly indicates that the geotiff package is missing in the lockfile.

If I install the geotiff package manually — which is unnecessary, as I don't require GeoTIFF support — it triggers a series of dependency resolution issues. Ultimately, this prevents the vitest package from being installed, so my unit tests can no longer run.

I reviewed the original issue (#510). The problems can be resolved by simply adding "skipLibCheck": true to the TypeScript compiler options in tsconfig.json. I think there are only a few rare cases where type safety need to be ensured throughout the whole dependency graph. For those rare cases, required dependencies can be explicitly installed, satisfying the compiler without impacting projects that don’t need them.

Edit:
The root cause for the dependency resolution issues was something else. Anyway, the requirement to save geotiff to my dependencies just for the typings of another dependency feels wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions