Setting the environment in local system

Development
21

Sure sir

22

Thank you sir, After following the instructions provided here, its working!!

23

hi I am facing this error pls help me out

image
image1262×40 3.09 KB

24

actually it builds correctly but still says ->

image
image1261×68 4.59 KB

25

I assume you are on Linux, So try installing libxshmfence1

sudo apt install libxshmfence1
26

And please when posting error messages copy and paste text instead of taking screenshots.

UPD
Even better, try googling the error first

27

I am getting this error nd i m on windows 10 @krishna

H:\Gsoc22\joplin\packages\app-desktop>yarn start
Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] ...

I tried to find a sol but seems no1 has posted it :- yarnpkg - Run script before installing packages with nodeLinker set to node-modules - Stack Overflow

28

Remove the current node_modules folder, then:

yarn cache clean && yarn install

If it didn't work check this discussion.

29

if there is no node_modules folder in the app-desktop package despite running yarn from the root, then do we need to run yarn install in app-desktop folder too?

actually i want to run the desktop version

30

Install from root, run from package. Have you tried @krishna's suggestion?

Otherwise post the full log of yarn install from the project root here.

31

Is there any docker command for setting up the project ?

32

No. All set up steps are in BUILD.md

33

I have followed all of them but ended up seeing errors like this ->

H:\Gsoc22\joplin\packages\app-desktop>npm start

@joplin/app-desktop@2.7.14 start
gulp build && electron . --env dev --log-level debug --no-welcome --open-dev-tools

'gulp' is not recognized as an internal or external command,
operable program or batch file.

nd yarn start gives

H:\Gsoc22\joplin\packages\app-desktop>yarn start
Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] ...

34

I don't think there is any npm start in build.md at all so not sure why you are running it?

running an install might help

You did yarn install from the root, right? - Also in case you have broken the package files somehow make sure you do it from a freshly cloned version just in case.

Also it is far easier to read things if you put logs and console outputs into code fence blocks (triple backtick ```)

35

@Daeraxa can we hv a quick 5 min meet i would share my screen nd tell u the things...
It would be more understandable

36

Just do the following steps and paste the output here if it doesn't work (if it fails at yarn install then stop there, don't continue or try to fix anything).

  • Create a dir that you want to work in (that has no spaces in your path)
  • git clone <url you forked joplin to>
  • cd joplin
  • yarn install
  • cd packages\app-desktop
  • yarn start
37

Ok :+1: