Thomas Hallock

not failing in module scope when run in node

3

For universal (a.k.a. "isomorphic") rendering: Even though this is a web-only module, it's important to not fail when imported server-side, because sometimes that's where components get rendered.

This seems like a more sensible default. Should be published with the next major release since it is a breaking change to any dependent that doesn't explicitly set this config...

using set -e instead of short-circuit evaluation to exit early on failure

1

added [`set -e`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) at the top of the script and removed ` &&` suffix from the end of every line.

fix: path resolution for html export

1

addresses the bug described in https://github.com/jsonresume/resume-cli/issues/493

The intention here is to gate PRs with tests, and run semantic release when a new release is drafted. I've tested a bit with [act](https://github.com/nektos/act), but we'll need to merge...

custom importers and exporters

8

Similar to how themes are implemented as separate packages, it would be nice to have community-developed importers and exporters in order to implement interoperability with other resume formats, e.g. h-resume...

proposal: embed original data into output

2

* for PDFs, we can use [XMP](https://en.wikipedia.org/wiki/Extensible_Metadata_Platform) * for HTML, we can use a meta or script tag. For example: * `

schema@ draft-7, no longer exporting validator, using jest for tests

17

separating all these things is a big difficult so grouping them in the same branch for this PR. Also, `ajv` wouldn't work until I said that the schema was draft-7....

failing test script if there is lint in the code or in the schema

8

I recommend merging https://github.com/jsonresume/resume-schema/pull/378 first