Skip to content

Releases: jdan/cleaver

v0.8.6

02 Dec 21:47
Compare
Choose a tag to compare

This release fixes a few security vulnerabilities in:

v0.8.5

18 Jun 07:59
Compare
Choose a tag to compare

Fix deprecation warning. Issue #171 via #172. Thanks to @kyuumeitai

Hotfixing 0.8.3

12 Jan 07:35
Compare
Choose a tag to compare

Just everything from https://github.com/jdan/cleaver/releases/tag/v0.8.3, but this time w/o error when trying to load local theme

v0.8.3

12 Jan 07:13
Compare
Choose a tag to compare
v0.8.3 Pre-release
Pre-release

Fixes:

  • update instructions on updating cleaver [@adriens]
  • fixing bug with progress bar not visible in default theme [@barneyb]
  • treating local theme file not found as remote theme 404 (just ignore) [@nuno-silva18]
  • syncing version in npm and in package.json in github

As always, you can upgrade cleaver with the following:

npm update -g cleaver

This release has an issue.
When you run with local theme you'll see

   if (err.code === 'ENOENT') {
           ^

TypeError: Cannot read property 'code' of null
    at {…}/cleaver/lib/helper.js:188:12

This is fixed in https://github.com/jdan/cleaver/releases/tag/v0.8.4

v0.7.7

24 Dec 20:50
Compare
Choose a tag to compare

Notes:

  • Fixes a bug where cleaver would crash on unrecognized languages for github flavored markdown cf79c02

As always, you can upgrade cleaver with the following:

npm update -g cleaver

0.7.5

03 Dec 14:26
Compare
Choose a tag to compare
  • Watch for stylesheet changes (#120)
  • Fix background color issue after fullscreen (#132)
  • Upgrade highlight.js to version 9.0.0 (#133)

Special thanks to @gabeboning, @yielder, and @omarkhan for doing all of the work in this release!

v0.7.2

06 Sep 19:45
Compare
Choose a tag to compare

A couple new features!

npm update -g cleaver
  • Support for weibo and github usernames in the author field. 06d9e6d 0d025db (#92) (#96)
  • Displaying ENOENT errors explicitly d685ed9 (#94)
  • Support for multiple input documents cleaver file1 file2 8e075bc
  • Ability to specify cleaver options for the command line cleaver file --output=slides.html e848dfb (#95)

Happy hacking!
@jdan

v0.6.0

03 Feb 22:49
Compare
Choose a tag to compare

Happy to announce a new cleaver update :)

npm update -g cleaver

Beyond several CSS performance tweaks, cleaver slides are now page-sized by default and arrange themselves a little differently (no more crazy DOM manipulation).

The results are improved performance, and easy-to-implement beautiful full-bleed slides (thanks Medium for the image):

full bleed

You can access slides more easily in your stylesheets like so:

#slide-2 {
  color: #eee;
  background: url('trees.jpg');
  background-size: cover;
}

I hope you'll play around with the new markup, but otherwise existing slideshows will look exactly as they did before this release. If you've written a theme, you may need to modify your templates to support the new slide layout.

Big thanks to @kcliu for improving options parsing as well.

Happy hacking!
@jdan

v0.5.0

09 Nov 18:02
Compare
Choose a tag to compare

Today I'm happy to announce cleaver v0.5.0.

$ npm update -g cleaver

This is a pretty hefty update with a lot of fixes and improvements, including:

cleaver-retro

  • Allow users to fetch resources by URL: style: http://jordanscales.com/soss/github_style.css
  • Fixed issues with building presentations located in foreign directories
  • Fixed issues loading resources located in foreign directories
  • Dedicated documentation

As always, everything is backwards compatible. Existing presentations will build the same.

I look forward to seeing how the community uses these features, which we'll keep hacking away on as cleaver nears a 1.0.0 release.

Big thanks to @matmuchrapna for his extended support and feedback with these changes.

Much <3,
@jdan

v0.4.2

04 Nov 22:21
Compare
Choose a tag to compare
$ npm update -g cleaver

Just a quick patch for weird tabindex behavior. This only affects users who use the tab key while navigating a cleaver presentation.

Thanks to @redtrumpet for first pointing this out in issue #32.

As always, with <3,
@jdan