Releases: saberland/saber
Releases · saberland/saber
saber v0.4.10
BREAKING CHANGES
- Now we use
static
folder to store static files whilepublic
folder is used to output HTML files and static assets. To migrate from previous version, please do:Don't forget to addmv public static rm -rf .saber/public
public
to your.gitignore
as well. For theme authors, you should also usestatic
folder instead ofpublic
folder.
New Features
ctx.setHead
andctx.setRootComponent
insaber-browser.js
, instead of directly mutatingrootOptions.head
, usectx.setHead
instead. docs
Bug Fixes
- A bug in
--lazy
mode: #139
saber@0.4.8
Bug Fixes
- Fix #67: Renaming/deleting markdown file breaks reloading (@MarchWorks)
saber@0.4.8-canary.2
0.4.8-canary.2 (2019-05-01)
Bug Fixes
saber-utils@0.1.1-canary.0
0.1.1-canary.0 (2019-05-01)
Note: Version bump only for package saber-utils
saber-markdown@0.0.4-canary.0
0.0.4-canary.0 (2019-05-01)
Note: Version bump only for package saber-markdown
create-site@0.2.3-canary.0
0.2.3-canary.0 (2019-05-01)
Note: Version bump only for package create-site
create-blog@0.2.3-canary.0
0.2.3-canary.0 (2019-05-01)
Note: Version bump only for package create-blog
saber v0.4.7
Enhancements
- Disable Vue production tips
Bug Fixes
- Make
page.contentType
default todefault
saber v0.4.6
BREAKING CHANGES
Line Highlighting CSS
We stopped injecting the CSS for code blocks since this release, which means if you want line highlighting to render properly you should consider using the package saber-highlight-css
:
yarn add saber-highlight-css
// saber-browser.js
import 'saber-highlight-css/default.css'
Bug Fixes
saber-plugin-transformer-pug v0.0.2
Bug Fixes
- the loader should only transform pug in .vue files (738b365)