Plasmic sync stuck in loop

Issues
21

can you do ./node_modules/.bin/plasmic sync

22

yeah I did that and then tried again to plasmic sync

23

ah I meant, instead of plasmic sync use ./node_modules/.bin/plasmic sync

24

Ah ok! Yes it’s syncing, can see the updates reflecting on local host

25

okay good… yeah somehow your plasmic global command is mapped to some plasmic executable that’s not the one in your node_modules/.bin :thinking_face:

26

is it concerning should it be fixed?

27

it is just annoying to have to use ./node_modules/.bin/plasmic all the time…

28

can you try where plasmic

29

No result

image.png

30

what about plasmic --version

31

0.1.293

32

yeah it is definitely a different executable, not sure from where… :thinking_face:

33

so for any plasmic command, I have to go through the ./node_modules/.bin/plasmic route?

34

Yeah

35

Same issue here with npm. Would be nice to have this fixed. It turned up with the latest update. Why are there 2 different versions?

image.png
image.png653×544 30.6 KB

image.png

36

it looks like we may not be detecting plasmic properly on windows… could you try running npm -g uninstall @plasmicapp/cli?

37

Will the push to github work correctly, considering this issue?

38

do you mean from the publish action? yes that’ll be fine. The issue is with your local development environment

39

Also have this problem on a mac but “./node_modules/.bin/plasmic sync” worked for me and plasmic sync does not.