You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run resume validate in a directory containing a file named resume.yml (I tried also using resume.yaml, same thing), I get this result:
$ resume validate
node:internal/process/promises:246
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: ENOENT: no such file or directory, stat 'resume.json'] {
errno: -2,
code: 'ENOENT',
syscall: 'stat',
path: 'resume.json'
}
Node.js v17.3.0
I also tried using resume validate resume.yml (passing the filename as argument), but I get the same error.
It appears like the YAML file is not read, even though this repository’s README indicates that YAML should be supported.
The text was updated successfully, but these errors were encountered:
i have as much no clue as you do, but after a while i stumbled across the --resume parameter.
To validate run: resume validate --resume resume.yaml
To save you the pain of what comes next:
The default theme just didn't work for me, it doesn't provide a index.js file in the root of the installed package and, against whatever the docs claim, it wasn't installed when installing resume-cli either.
So:
init a package.json in the dir that contains the resume.yaml to be able to install packages into the dir: npm init --yes
install a theme, eg: npm install jsonresume-theme-orbit
export the pdf: resume export --resume resume.yaml --theme orbit foo.pdf
But a html preview via resume serve --resume resume.yaml --theme orbit still fails 🤷
At this point I'm giving up.
I couldn't find any theme where the pdf export looks half decent... If you do, let me know 🙂
When I run
resume validate
in a directory containing a file namedresume.yml
(I tried also usingresume.yaml
, same thing), I get this result:I also tried using
resume validate resume.yml
(passing the filename as argument), but I get the same error.It appears like the YAML file is not read, even though this repository’s README indicates that YAML should be supported.
The text was updated successfully, but these errors were encountered: