search

wesbos / master-gatsby

slick slices eh
358 stars 388 forks source link

Why After npm run develop i have to wait 3 min to build #117

Open aragon000 opened 3 years ago

aragon000 commented 3 years ago

hi i have an issue with gatsby

un npm audit for details. aragon@User-PC:/mnt/c/Users/Aragon/Documents/pizza/gatsby$ npm start

slicks-slices-frontend@0.1.0 start npm run develop

slicks-slices-frontend@0.1.0 develop cross-env NODE_OPTIONS="-r esm" gatsby develop

success onPreExtractQueries - 0.045s success extract queries from components - 3.109s success write out requires - 0.091s success run static queries - 0.157s - 2/2 12.77/s success run page queries - 0.104s - 3/3 28.73/s ⠀ You can now view slicks-slices-frontend in the browser. ⠀
http://localhost:8000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema ⠀
http://localhost:8000/___graphql
⠀
Note that the development build is not optimized. To create a production build, use gatsby build
⠀
success Building development bundle - 73.712s

ANY SOLUTION?

Asjas commented 3 years ago

Your folder directory in the message you posted looks like this. Are you using WSL (Windows Subsystem for Linux)? @aragon000 

/mnt/c/Users/Aragon/Documents

If you are using WSL then you should move the project into the WSL Distro itself, if you try to access Windows files on /mnt/c from WSL then the speed becomes extremely slow. WSL is slow when accessing files that are stored on Windows.

The project files needs to exist directly in the WSL Distro itself - you should create a folder for projects in WSL and then clone or download the master-gatsby into WSL. The speed will then be faster when compiling the dev server 🙂