Skip to content

v2.0.8 [Windows 10] globally installed nodemon broken (looking for windows-kill.exe locally) #1872

@ericarthurc

Description

@ericarthurc

With the new 'windows-kill' merge in version 2.0.8 it brakes globally installed nodemon restarts. It says it is looking for the windows-kill binary in the local node_modules folder, but obviously if I am running nodemon from a global install, it's package wont be in the local node_modules

Here is the error I receive; and you can see I dont have nodemon installed locally on this project
nodemon2 0 8
nodemon2 0 8ver

Here is the same project using nodemon 2.0.7; and the global nodemon works fine
nodemon2 0 7

  • nodemon -v: 2.0.8
  • node -v: 16.4.0
  • Operating system/terminal environment: Windows 10
  • Command you ran: nodemon src/main.ts

Steps to reproduce

Install nodemon with npm i -g npm@latest, verify its version 2.0.8 with nodemon -v then run nodemon without a local project install

I want to clarify, that a local install within the project will work with v2.0.8; its just when you try to run it from a global only install

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions