Skip to content

Node 18 support broken #398

Description

@noahw3

Describe the bug

Starting with version 1.5.11, running with node 18 started failing with the error TypeError [ERR_INVALID_ARG_TYPE]: The "paths[0]" argument must be of type string. Received undefined.

I don't see any documentation about minimum supported node versions, and this broke in a patch update. It seems to be from a transitive dependency update (unplugin 3.3.0?). Was this intended?

If node 18 support has been dropped I think that's acceptable. However it should be documented and ideally happen with a major version bump.

Reproduction

Can provide if needed

System Info

System:
    OS: macOS 26.5.2
    CPU: (18) arm64 Apple M5 Pro
    Memory: 327.92 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.0 - /Users/noah.wilson/.nvm/versions/node/v18.20.0/bin/node
    npm: 10.5.0 - /Users/noah.wilson/.nvm/versions/node/v18.20.0/bin/npm
    pnpm: 10.34.1 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 152.0.7977.77
    Safari: 26.5.2

Used Package Manager

pnpm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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