wml watchman doesn't do anything on macOS

[MuhammadAhmed1994]

I have added links by using wml add, the links are also enabled when I run wml start. But when I run wml start it is not doing anything.

[hamzaazad]

I have the same issue, get resolved by adding WML/src dir to the watchman list.

watchman watch /Users/rcrabwu/.nvm/versions/node/v14.17.1/lib/node_modules/wml/src

[MuhammadAhmed1994]

Still not working for me

watchman watch /Users/{username}/.nvm/versions/node/v14.17.1/lib/node_modules/wml/src

failed to validate command: Could not resolve /Users/rcrabwu/.nvm/versions/node/v14.17.1/lib/node_modules/wml/src to the canonical watch path: open: /Users/rcrabwu/.nvm/versions/node/v14.17.1/lib/node_modules/wml/src: No such file or director

is there anything to do with nvm? I don't have nvm installed.
My wml path is /usr/local/lib/node_modules/wml/src

but watchman watch /usr/local/lib/node_modules/wml/src didn't work either.

[MuhammadAhmed1994]

Problem Solved!

Thanks for the direction @hamzaazad

I have tried these steps to resolve the issues

• Run watchman watch /usr/local/lib/node_modules/wml/src
• Addwatchman in Full disk access from setting > security and privacy.
• Also change the permission of your global node_modules on the safe.

[danzanzini]

I was having the same problem and just running watchman watch /usr/local/lib/node_modules/wml/src solved it for me.

Should this command be added to the README?

[ghost]

This should be automatic, but this repo seems to be no longer maintained.

I created something new called papapackage. It automatically finds and watches all your projects, you don't need to add anything!

[YOEL311]

In my case this command slove the problem

watchman watch /opt/homebrew/lib/node_modules/wml/src

[beyoursun]

I install wml by yarn, check yarn global dir:

yarn global dir # -> /Users/{username}/.config/yarn/global
# npm can run `npm prefix -g`

Then execute this command to solve the problem:

watchman watch /Users/{username}/.config/yarn/global/node_modules/wml/src

[amda-phd]

@beyoursun 's answer fixes the problem in macOS Monterrey 12.6. Thanks!