[email protected] compile:sass C:\Users\MICKEYDP\Desktop\natours node-sass sass/main.scss css/style.css

{ "status": 1, "file": "C:/Users/MICKEYDP/Desktop/natours/sass/main.scss", "line": 30, "column": 7, "message": "Function rgb is missing argument $blue.", "formatted": "Error: Function rgb is missing argument $blue.\n on line 30 of sass/main.scss\n>> rgb($color-primary-light, 0.8),\r\n ------^\n" } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] compile:sass: node-sass sass/main.scss css/style.css npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] compile:sass script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\MICKEYDP\AppData\Roaming\npm-cache_logs\2018-10-20T14_01_32_138Z-debug.log

As you can see, the nav bar links are overlapping the other elements even with the navigation bar not enabled and they are clickable making the interation with other elements impossible if they are under the links.

I tested the published version of the Natours page available at https://natours.netlify.com/ using google chrome on macOS.

Since I haven't reached the part of the course that the navbar was developed, I won't be able to find the most elegant solution for that.

Hey @jonasschmedtmann thanks for the amazing content. Your courses are extremely helpful. I wanted to jump into the project today for building Nexter to brush up on CSS grid and noticed that I couldn't run the included NPM scripts. I think you may have live-server installed globally which may be useful for some setups but I don't think that should be a requirement for running the app.

Also thought it might be handy to capture a package.lock so that if deps change in the future and introduce some weird breaking behavior (unlikely) that people are guaranteed to get working version numbers pulled down.

SASS Compile not working. I have followed the tutorial but it's showing multiple errors. Here is the Command line npm run compile:sass

It is coming up with these errors. An output directory must be specified when compiling a directory npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] compile:sass:node-sass sass/main.scss css/style.css` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] compile:sass script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Jahid\AppData\Roaming\npm-cache_logs\2018-05-03T20_17_13_135Z-debug.log`

I am also attaching the scirpt package.json file. { "name": "ui", "version": "1.0.0", "description": "Ui for QR Code generator", "main": "index.js", "scripts": { "compile:sass": "node-sass sass/main.scss css/style.css" }, "author": "Jahid Anowar", "license": "ISC", "devDependencies": { "node-sass": "^4.9.0" } }

This problem is caused because devserver needs the lib "live-server". This pr fixes it

yarn start
yarn run v1.17.3
$ npm-run-all --parallel devserver watch:sass
$ live-server --browser=firefox
$ node-sass sass/main.scss css/style.css -w
/bin/sh: 1: live-server: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "devserver" exited with 127.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hi Jonas!

I hope your are doing great. First of all I want to thank you for your well designed course. So far I have learned a ton of awesome new stuff and I am looking forward to continue.

Like a lot of other people I ran into the same issue using the --watch flag. After watching your video again and paying more attention it works like a charm! VSC is such a great editor. I love the build in terminal function! Comes in really handy.

But anyway, I would like to make a comment on your 2nd solution. When using the two lines of code you provided the terminal throws an error. When the two lines are separated by a coma everything is compiled well.

Best, Jan

Hi, I have come across a problem. I am now on natours sass section. I can't set the width of the columns with calc function. It shows error in chrome dev tool.

Please help me.

In the desktop breakpoint, if you position the cursor under the logo, you can see the cursor changing to hand, because the menu items are there, I used display none and after display block, but the solution did not work, because the animation does not work, so I changed for visibility: hidden, and after visibility:visible;

I tested and everything works ok !

Homepage still has clickable navigation links since width of 0 on parent element didn't fully hide the child anchor element due to the padding that was being applied. This fixes it and fixes a typo on the home page.

The Natours project. On Firefox, the rotating cards don't have perspective when "backface-visibility" property is hidden.

Please clarify what is the solution here, for the cards to have perspective?

I've changed the padding of the heading of about section from 20rem to 25rem, Because you can see screen, less than 600px, the heading of about section & the header section has no padding in between. Thanks,

When trying to run live server with npm run or npm start,

Microsoft Windows Defender gives this threat warning and, compilation of sass and live server crashes

CVE-2010-3971