Do you think it's a good idea to enable integration with GitHub Pages? This would allow devs to deploy their resume right from the command line using gh-pages

DONE Compiled successfully in 9128ms

Listening at http://localhost:8080

Connected to server ... Exporting ... Finished exports.

Downloads\resumes\best-resume-ever>

BUG

Issue

Blank review on Linux and blank PDFs on export

Info

• Operating System: LINUX
• Node-Version: v8.8.1

Reproduce

Step 1: Done the editing in resume folder

Step 2: Running the review on dev server

The review runs on host 8080 but when I click on the template, it is blank

Step 3: npm run export creates the pdf in PDF folder but all the pdf are blank

Case

• BUG

Issue

When previewing or exporting to PDF, only about 3/4ths of the resume is shown.

Info

• Operating System: Windows
• Node-Version: v8.5.0

Reproduce

npm run dev npm run export

Version 2.5.3 of vue was just published.

The version 2.5.3 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of vue.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

Version 2.5.3 of vue-template-compiler was just published.

The version 2.5.3 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of vue-template-compiler.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.0.0 of html-webpack-plugin was just published.

The version 3.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of html-webpack-plugin.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

Case

• BUG

Issue

no PDF file in pdf/ folder after npm run export

Info

• Operating System: WINDOWS10
• Node-Version: v8.9.4

Reproduce

npm run export
i ｢wdm｣: Compiled successfully.                                                                                                                                                                   
> Listening at http://localhost:8080                                                                                                                                                              
                                                                                                                                                                                                  
Connected to server ...                                                                                                                                                                           
Exporting ...                                                                                                                                                                                     
Finished exports.                                                                                                                                                                                 
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              
(node:10632) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero 
exit code.                                                                                                                                                                                        
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              
(node:10632) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 7): AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "yarn install" or "npm inst
all"                                                                                                                                                                                              

Case

• ENHANCEMENT

Issue

born ... in ... not translated in other language ( at least in french )

Info

• Operating System: W10 Pro
• Node-Version: 8.9.0

Case

• BUG

Issue

Trying to execute npm run dev and getting an error message. Tried to clone from the original repository and I'm getting the same error.

Info

• Operating System: Linux (Ubuntu 16.04.3)
• Node-Version: 8.9.0

Reproduce

0 info it worked if it ends with ok
1 verbose cli [ '/home/gabrielcs/.nvm/versions/node/v8.9.0/bin/node',
1 verbose cli   '/home/gabrielcs/.nvm/versions/node/v8.9.0/bin/npm',
1 verbose cli   'run',
1 verbose cli   'dev' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle [email protected]~predev: [email protected]
6 verbose lifecycle [email protected]~predev: unsafe-perm in lifecycle true
7 verbose lifecycle [email protected]~predev: PATH: /home/gabrielcs/.nvm/versions/node/v8.9.0/lib/node_modules/npm/bin/node-gyp-bin:/home/gabrielcs/Documentos/WebSites/awesome-cv-creator/node_modules/.bin:/home/gabrielcs/.nvm/versions/node/v8.9.0/bin:/home/gabrielcs/bin:/home/gabrielcs/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin
8 verbose lifecycle [email protected]~predev: CWD: /home/gabrielcs/Documentos/WebSites/awesome-cv-creator
9 silly lifecycle [email protected]~predev: Args: [ '-c', 'check-node-version --node ">= 8.0.0"' ]
10 silly lifecycle [email protected]~predev: Returned: code: 1  signal: null
11 info lifecycle [email protected]~predev: Failed to exec predev script
12 verbose stack Error: [email protected] predev: `check-node-version --node ">= 8.0.0"`
12 verbose stack Exit status 1
12 verbose stack     at EventEmitter.<anonymous> (/home/gabrielcs/.nvm/versions/node/v8.9.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
12 verbose stack     at emitTwo (events.js:126:13)
12 verbose stack     at EventEmitter.emit (events.js:214:7)
12 verbose stack     at ChildProcess.<anonymous> (/home/gabrielcs/.nvm/versions/node/v8.9.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
12 verbose stack     at emitTwo (events.js:126:13)
12 verbose stack     at ChildProcess.emit (events.js:214:7)
12 verbose stack     at maybeClose (internal/child_process.js:925:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
13 verbose pkgid [email protected]
14 verbose cwd /home/gabrielcs/Documentos/WebSites/awesome-cv-creator/resume
15 verbose Linux 4.10.0-38-generic
16 verbose argv "/home/gabrielcs/.nvm/versions/node/v8.9.0/bin/node" "/home/gabrielcs/.nvm/versions/node/v8.9.0/bin/npm" "run" "dev"
17 verbose node v8.9.0
18 verbose npm  v5.5.1
19 error code ELIFECYCLE
20 error errno 1
21 error [email protected] predev: `check-node-version --node ">= 8.0.0"`
21 error Exit status 1
22 error Failed at the [email protected] predev script.
22 error This is probably not a problem with npm. There is likely additional logging output above.
23 verbose exit [ 1, true ]

Case

Bug

Issue

Unable to run in Windows 7

Info

• Operating System: Windows 7
• Node-Version: 6.11.3
• NPM Version: 3.10.10

Log file output:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'dev' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle [email protected]~predev: [email protected]
6 silly lifecycle [email protected]~predev: no script for predev, continuing
7 info lifecycle [email protected]~dev: [email protected]
8 verbose lifecycle [email protected]~dev: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~dev: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\ma331192\src\best-resume-ever\node_modules\.bin;%SystemRoot%\system32\WindowsPowerShell\v1.0\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x86)\Sennheiser\SoftphoneSDK\;%USERPROFILE%\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\PuTTY\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Java\bin;C:\apache-maven-3.3.9\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\nodejs\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Sennheiser\SoftphoneSDK\;C:\Users\ma331192\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Users\ma331192\AppData\Local\Programs\Git\cmd;C:\Users\ma331192\AppData\Local\atom\bin
10 verbose lifecycle [email protected]~dev: CWD: C:\Users\ma331192\src\best-resume-ever
11 silly lifecycle [email protected]~dev: Args: [ '/d /s /c', 'node build/dev-server.js' ]
12 silly lifecycle [email protected]~dev: Returned: code: 1  signal: null
13 info lifecycle [email protected]~dev: Failed to exec dev script
14 verbose stack Error: [email protected] dev: `node build/dev-server.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid [email protected]
16 verbose cwd C:\Users\ma331192\src\best-resume-ever
17 error Windows_NT 6.1.7601
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
19 error node v6.11.3
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error [email protected] dev: `node build/dev-server.js`
22 error Exit status 1
23 error Failed at the [email protected] dev script 'node build/dev-server.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 best-resume-ever package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     node build/dev-server.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs best-resume-ever
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls best-resume-ever
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Reproduce

npm run dev

EDIT by @pubkey : Format bash-output.

This PR contains:

This pull request contains a standard code of conduct document, a document that briefly outlines some tips on how to contribute to this project and a couple of long line code smells that were cleaned up.

Describe the problem you have without this PR

I didn't have any issues.

I noticed that in the skills section, when you type a one letter skill or programming language it creates a formatting issue. I was not able to fix it, but I added a comment to highlight the issue and bypass it by adding a "." to the end.

This PR contains:

Describe the problem you have without this PR

This PR contains:

• A typo-fix of the license file
• Improved "how to use" section in the readme for Windows users

Describe the problem you have without this PR

Without the fix to the .eslintrc file, when using Windows, many linting errors come up. There is a blurb to show WIndows users how to fix the .eslintrc file to be able to run npm dev

Case

HELP QUESTION

Issue

I tried master and all different branches on different systems with different nodejs versions and I no longer can use your amazing script. Around year ago I used it to generate CV and I got hired instantly. Now I want to help non-technical friend to make best-resume-ever and I am wondering what I could do to help fix the master. Or maybe @salomonelli could point me to the working branch for modern systems. Year ago it worked :(

Info

• Operating System: Linux
• Node-Version: node16/node17/node18/node19

Reproduce

[TO BE FILLED IN]

A suggestion on docs about running the project

I try to follow the instructions to run the project on vscode but get the error: (linebreak-style) Expected linebreaks to be ‘CRLF‘ but found ‘LF‘ linebreak-style. Then i find out the reason is using vscode to run this project. So i think maybe announce this situation in docs maybe helpful for windows users and people not familar with project . And the solution is very simple, only one line code can solve the problem

Solution

edit the file .eslintrc and change the attribute linebreak-style in rules as follow： "rules": { "linebreak-style": [0,"error", "windows"], } Then you can run npm run dev successfully.