When running `wml start` nothing happen #17

idangozlan · 2017-10-23T23:10:15Z

I use to work with wml start on my old mac, then switch to a new one, now wml start doesnt do nothing. Anyway to print debug log or something that can lead to the problem?

The text was updated successfully, but these errors were encountered:

Scit · 2018-02-14T12:35:14Z

Having the same.

Ubuntu 16.04, watchman v. 4.9.1

madflanderz · 2018-04-18T10:04:23Z

I had the same problem. In my case i had a bad npm environment and i installed wml with sudo. If you did this you have to use sudo also when you add links:

sudo npm install -g wml
sudo wml add ./src ./dest
wml list
wml start

Better solution is use node version manager. Then you don't need to install packages with sudo.

henninghall · 2018-11-23T09:17:54Z

Same problem on ubuntu, works perfectly on mac

henninghall · 2018-11-23T13:10:02Z

Solved it by installing the latest version of watchman

bantingGamer · 2019-03-07T14:01:34Z

of

what version of watchman did you install? becasue i still just have a cursor flashing...

LordDraagonLive · 2019-06-03T11:01:31Z

I'm facing thee same issue in windows 10

pmontu · 2019-06-11T05:55:25Z

I am facing the same issue. I did not try installing watchman again. I am using bionic beaver

SackeyDavid · 2019-06-20T11:37:14Z

Pleasse how do we fix it on windows 10?

SackeyDavid · 2019-06-20T13:31:36Z

fixed using npm-link https://medium.com/dailyjs/how-to-use-npm-link-7375b6219557 on Windows 10. But this is problematic because npm-link which uses symbolic linking doesn't work with the metro bundler facebook/metro#1.

pmontu · 2019-06-24T05:24:15Z

I moved from node 9 to 10(using nvm) and installed wml again. now wml opens up super fast.

SackeyDavid · 2019-06-24T11:55:16Z

I moved from node 9 to 10(using nvm) and installed wml again. now wml opens up super fast.

Hmm, thanks @pmontu for the reply. I'm using node version 12.4.0 on Windows 10 and it's still not working with the metro bundler. Are you using Windows 10 please?

MirceaTheOldMan · 2019-06-27T14:44:27Z

I've tried with node 8.16.0, 10.16.0 and 12.4.0 but it doesn't do anything when I write wml start.
All the other commands worked fine. wml add created that .watchmanconfig file.
I'm using Windows 10 Home, watchman 4.9.4

SackeyDavid · 2019-06-28T11:56:18Z

I've tried with node 8.16.0, 10.16.0 and 12.4.0 but it doesn't do anything when I write wml start.
All the other commands worked fine. wml add created that .watchmanconfig file.
I'm using Windows 10 Home, watchman 4.9.4

Hi @MirceaTheOldMan, after countless futile attempts to fix this problem on windows 10, I've finally decided to work on Mac OS. And it works fine there.

Now, I want to work on a library to fix that for windows 10. I'll like some interested persons to collaborate with me on this. Since facebook metro hasn't said they plan working on symlinks and wix/wml hasn't said anything too, I think something needs to done for windows 10 users.

stackoverjoe · 2019-07-02T02:55:50Z

I've tried with node 8.16.0, 10.16.0 and 12.4.0 but it doesn't do anything when I write wml start.
All the other commands worked fine. wml add created that .watchmanconfig file.
I'm using Windows 10 Home, watchman 4.9.4

I am having the exact same issue. Can run all commands fine except start. The problem seems to lie in watchman for windows 10.

MirceaTheOldMan · 2019-07-02T12:23:19Z

I've tested wml start on OSX and Linux and they work fine. What if this is somehow related to the way the path (as parameters for the add command) is written in OSX / Linux versus Windows?

MirceaTheOldMan · 2019-07-09T14:33:14Z

I found a partial solution for "Windows":

Install WSL (Windows Subsystem for Linux);
Install Ubuntu and update it's packages;
Install watchman;
Install nodejs (no specific version mandatory) inside Ubuntu
and lastly. Install wml inside Ubuntu.

Note:
You'll only be able to use wml inside Ubuntu, meaning that the project (the watched folder and the destination) must be inside Ubuntu's root folder or it's child folders.
Make sure to read WSL's documentation because with latest version of windows(1903) you can view that folder and even use VS Code to create and edit files in that folder, from within Windows, not from Linux.
Conclusion:
You just use the whole WSL with Linux console to watch the folder that needs duplication. The other part of code implementation can be easily done from VS Code.

LordDraagonLive · 2019-07-10T12:57:21Z

That's lot of steps to install a package but really grateful for your effort. I hope will find a more simpler way to achieve this.

wushq5 · 2019-08-15T09:07:35Z

add the wml/src dir to watchman list will do, like this
watchman watch /Users/rcrabwu/.nvm/versions/node/v8.9.0/lib/node_modules/wml/src

SevenZark · 2019-12-05T22:10:02Z

I having this issue in Windows 10. wml start just results in a blinking cursor. No changes are detected. The software does nothing. Since this issue has been open for about two years, I guess I'm not hopeful of anyone caring enough to fix..? I sure wish I knew how myself.

krunaldholakia01 · 2019-12-28T04:26:03Z

add the wml/src dir to watchman list will do, like this
watchman watch /Users/rcrabwu/.nvm/versions/node/v8.9.0/lib/node_modules/wml/src

Thanks @wushq5 !
->First I downloaded latest version of watchman and added it to path environment variable.
-> Installed wml using npm globally
->Then added link to my node_module ( "wml add ..\common .\node_modules\@wow\common ")

I started using wml start but there was blank screen with cursor blinking.
Last I tried adding wml src folder as per your direction like this
-> watchman watch C:\Users\%user%\AppData\Roaming\npm\node_modules\wml\src
That solved issue for me on Windows 10.
☺☺☺

SackeyDavid · 2019-12-28T10:21:09Z

Wow, great

…

On Sat, Dec 28, 2019, 04:26 Krunal Dholakia ***@***.***> wrote: add the wml/src dir to watchman list will do, like this watchman watch /Users/rcrabwu/.nvm/versions/node/v8.9.0/lib/node_modules/wml/src Thanks @wushq5 <https://github.com/wushq5> ! ->First I downloaded latest version of watchman and added it to path environment variable. -> Installed wml using npm globally ->Then added link to my node_module ( "wml add ..\common .***@***.***\common ") I started using wml start but there was blank screen with cursor blinking. Last I tried adding wml src folder as per your direction like this -> watchman watch C:\Users%user%\AppData\Roaming\npm\node_modules\wml\src That solved issue for me on Windows 10. ☺☺☺ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEFE6MDXJDGQNVPOAQOWGQDQ23INZANCNFSM4EAOPL5A> .

…press fixes wix-incubator#17

hodev-dev · 2020-10-31T17:39:44Z

same problem windows 10 latest version of watchman installed with chocco

huhuang03 · 2021-04-04T11:59:23Z

add the wml/src dir to watchman list will do, like this
watchman watch /Users/rcrabwu/.nvm/versions/node/v8.9.0/lib/node_modules/wml/src

Thanks @wushq5 !
->First I downloaded latest version of watchman and added it to path environment variable.
-> Installed wml using npm globally
->Then added link to my node_module ( "wml add ..\common .\node_modules@wow\common ")

I started using wml start but there was blank screen with cursor blinking.
Last I tried adding wml src folder as per your direction like this
-> watchman watch C:\Users%user%\AppData\Roaming\npm\node_modules\wml\src
That solved issue for me on Windows 10.
☺☺☺

Yes, it can work, And If not do that, the error log is this on my pc, which I use the wml in F:\wml:

PS F:\> wml start
client subscribe end called Error: class RootResolveError: RootResolveError: unable to resolve root F:\wml\src: RootResolveError: directory F:/wml/src is not watched
    at BunserBuf.<anonymous> (F:\wml\node_modules\fb-watchman\index.js:95:23)
    at BunserBuf.emit (events.js:310:20)
    at BunserBuf.process (F:\wml\node_modules\bser\index.js:289:10)
    at F:\wml\node_modules\bser\index.js:244:12
    at processTicksAndRejections (internal/process/task_queues.js:79:11) {
  watchmanResponse: {
    version: '20201213.172817.0',
    error: 'class RootResolveError: RootResolveError: unable to resolve root F:\\wml\\src: RootResolveError: directory F:/wml/src is not watched'
  }
}

quinnwai · 2021-06-24T17:09:53Z

If there's no source file in

watchman watch /Users/rcrabwu/.nvm/versions/node/v8.9.0/lib/node_modules/wml/src

find where your wml/src is installed. For me it was in ~/.config/yarn/global/ since I used yarn global install wml to install the package.

etash47 · 2022-06-08T23:32:27Z

If there's no source file in

watchman watch /Users/rcrabwu/.nvm/versions/node/v8.9.0/lib/node_modules/wml/src

find where your wml/src is installed. For me it was in ~/.config/yarn/global/ since I used yarn global install wml to install the package.

I had trouble finding where my installation was. I had installed wml globally as well, so I used npm config get prefix to find the npm in use, and then appended lib/node_modules/wml/src to that path, and then did what QuinnWai said

motornyi pushed a commit to motornyi/wml that referenced this issue Oct 13, 2020

fix(calendar): workaround RN43 bug that triggers exception on number …

8f14cf7

…press fixes wix-incubator#17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

When running `wml start` nothing happen #17

When running `wml start` nothing happen #17

idangozlan commented Oct 23, 2017

Scit commented Feb 14, 2018

madflanderz commented Apr 18, 2018

henninghall commented Nov 23, 2018

henninghall commented Nov 23, 2018

bantingGamer commented Mar 7, 2019

LordDraagonLive commented Jun 3, 2019

pmontu commented Jun 11, 2019

SackeyDavid commented Jun 20, 2019

SackeyDavid commented Jun 20, 2019 •

edited

Loading

pmontu commented Jun 24, 2019

SackeyDavid commented Jun 24, 2019 •

edited

Loading

MirceaTheOldMan commented Jun 27, 2019

SackeyDavid commented Jun 28, 2019 •

edited

Loading

stackoverjoe commented Jul 2, 2019

MirceaTheOldMan commented Jul 2, 2019

MirceaTheOldMan commented Jul 9, 2019

LordDraagonLive commented Jul 10, 2019

wushq5 commented Aug 15, 2019

SevenZark commented Dec 5, 2019

krunaldholakia01 commented Dec 28, 2019 •

edited

Loading

SackeyDavid commented Dec 28, 2019 via email

hodev-dev commented Oct 31, 2020

huhuang03 commented Apr 4, 2021 •

edited

Loading

quinnwai commented Jun 24, 2021

etash47 commented Jun 8, 2022

When running wml start nothing happen #17

When running wml start nothing happen #17

Comments

idangozlan commented Oct 23, 2017

Scit commented Feb 14, 2018

madflanderz commented Apr 18, 2018

henninghall commented Nov 23, 2018

henninghall commented Nov 23, 2018

bantingGamer commented Mar 7, 2019

LordDraagonLive commented Jun 3, 2019

pmontu commented Jun 11, 2019

SackeyDavid commented Jun 20, 2019

SackeyDavid commented Jun 20, 2019 • edited Loading

pmontu commented Jun 24, 2019

SackeyDavid commented Jun 24, 2019 • edited Loading

MirceaTheOldMan commented Jun 27, 2019

SackeyDavid commented Jun 28, 2019 • edited Loading

stackoverjoe commented Jul 2, 2019

MirceaTheOldMan commented Jul 2, 2019

MirceaTheOldMan commented Jul 9, 2019

LordDraagonLive commented Jul 10, 2019

wushq5 commented Aug 15, 2019

SevenZark commented Dec 5, 2019

krunaldholakia01 commented Dec 28, 2019 • edited Loading

SackeyDavid commented Dec 28, 2019 via email

hodev-dev commented Oct 31, 2020

huhuang03 commented Apr 4, 2021 • edited Loading

quinnwai commented Jun 24, 2021

etash47 commented Jun 8, 2022

When running `wml start` nothing happen #17

When running `wml start` nothing happen #17

SackeyDavid commented Jun 20, 2019 •

edited

Loading

SackeyDavid commented Jun 24, 2019 •

edited

Loading

SackeyDavid commented Jun 28, 2019 •

edited

Loading

krunaldholakia01 commented Dec 28, 2019 •

edited

Loading

huhuang03 commented Apr 4, 2021 •

edited

Loading