Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suniti heading font changes to ariel, h2 color changed to black. #119

Closed
wants to merge 1 commit into from
Closed

suniti heading font changes to ariel, h2 color changed to black. #119

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions npm-debug.log
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
0 info it worked if it ends with ok
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You seem to have added this extra npm-debug.log file in your commit. Make sure you remove this, as it would not be required. To see what I am talking about, you can click on that Files Changed button at the top of your PR.
When you are adding files to a commit, you can run git status to see how many files have changed or been staged for the commit. If you changed multiple files, but only want to commit one, say File1.md. You can do that by running add File.md instead of add .. The . in the latter means that it adds all the files that have changed.

1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/share/npm/bin/node-gyp-bin:/home/suniti/Open-Source-Challenge/node_modules/.bin:/home/suniti/anaconda3/bin:/home/suniti/anaconda3/condabin:/opt/firefox/firefox:/home/suniti/bin:/home/suniti/.local/bin:/opt/firefox/firefox:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/user_directory/Android/Sdk/tools:/home/user_directory/Android/Sdk/platform-tools
10 verbose lifecycle [email protected]~start: CWD: /home/suniti/Open-Source-Challenge
11 silly lifecycle [email protected]~start: Args: [ '-c', 'node index.js' ]
12 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `node index.js`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at EventEmitter.emit (events.js:214:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at ChildProcess.emit (events.js:214:7)
14 verbose stack at maybeClose (internal/child_process.js:925:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/suniti/Open-Source-Challenge
17 error Linux 4.15.0-34-generic
18 error argv "/usr/bin/node" "/usr/bin/npm" "start"
19 error node v8.10.0
20 error npm v3.5.2
21 error code ELIFECYCLE
22 error [email protected] start: `node index.js`
22 error Exit status 1
23 error Failed at the [email protected] start script 'node index.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the acm package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node index.js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs acm
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls acm
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
6 changes: 3 additions & 3 deletions public/style.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,11 +60,11 @@ a:focus{
}

h1,h2,h3,h4,h5,h6{
font-family: 'Varela', sans-serif;
font-family: comic-sans;
}

h2 {
color: #313338;
color: #ffffff;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#ffffff can also be written as #fff, it means the same thing. Plus #fff is actually white and not black. But I don't see anything changing because of this?

font-size: 30px;
font-weight: 700;
line-height: 40px;
Expand Down Expand Up @@ -1775,4 +1775,4 @@ div[data-dimension] {
@media(max-width:320px ){


}
}