Releases: welaika/wordless
3.0.1
Added
- 3bf4e7c Hotfix: documentaion node - Add documentation about the node's required version.
Fixed
3.0.0
Full diff from previous version @ 2.7.0...3.0.0
Breaking changes
- HAML is no longer supported
- Themes created with Wordless <3.0.0 are not compatible with Wordless >=3.0.0 due to the changed scaffold
If you are interested in updating a project you have to study the new scaffold and update it by hand. This will be a hard work and we cannot provide an automagic upgrade for such a big change.
Highlights
- bump required node version to current LTS
- support NVM adding nvmrc
- Stylelint is supported and configured by default
- coffeescript will be polyfilled and transpiled by babel by default (w/ browserslist help)
- Add default configuration for browserslist
- lint and update default sass (with an image to test image url rewriting done by Webpack)
- refactor folder structure (partially fixing #239)
- use mini-css-extract-plugin fix #236
- readme updated
- documentation @ https://wordless.readthedocs.io/en/latest/ updated and improved
- added nodejs section
- added documentation about how to use multi-entries bundles
- updated all the references to the old scaffold
- more! Take a look at it: it's a big effort to keep it up and good :)
- Webpack configuration now supports multi-entries by default (starts with a single one, but ready to work with multiple)
- updated all the JS deps
- updated all the PHP deps
v2.7.0
The main shipped feature is a new filter wordpress_pug_configuration
that let developer overwrite pug configurations inside the theme. Documentation added at https://wordless.readthedocs.io/en/latest/_pages/usage/filters.html.
Thanks to @juankk for his contibution.
Commits highlights
v2.5.0
Wordless 2.5 deprecates the old ruby preprocessors support. It is disabled by
default. If you need to develop an old theme you need to explicitly activate
them by setting the following in your wp-config.php
define('WORDLESS_LEGACY', true);
Wordless 3 is planned to completely remove this support.
v2.4.2
v2.4.0
This is a performance related update.
- 8357d8a assume plugin's composer autoloader will behave as in production env (ref)
- eec9872 if environment is staging or production, then switch on Optimizer (Phug ref)
\Phug\Optimizer
From now on if Wordless will find ENVIRONMENT
set up as a constant (in wp-config.php
) or as an environment variable and its value is staging
or production
, then the rendering optimizer will be automatically used.
Updated the following vendors through composer:
- Updating nodejs-php-fallback/nodejs-php-fallback (1.3.1 => 1.4.1)
- Updating symfony/polyfill-mbstring (v1.7.0 => v1.9.0)
- Updating phug/event (0.1.1 => 0.1.2)
- Updating phug/lexer (0.5.21 => 0.5.28)
- Updating phug/formatter (0.5.41 => 0.5.42)
- Installing symfony/polyfill-php72 (v1.9.0)
- Updating symfony/var-dumper (v3.4.4 => v4.1.5)
- Updating phug/renderer (0.4.0 => 0.4.5)
- Updating phug/phug (0.3.1 => 0.3.2)
- Updating js-phpize/js-phpize (1.14.0 => 2.0.0)
- Updating js-phpize/js-phpize-phug (1.1.7 => 2.0.0)
- Updating pug-php/pug (3.1.6 => 3.2.0)
- Updating mobiledetect/mobiledetectlib (2.8.30 => 2.8.33)
v2.3.2
v2.3.1
- publish https://wordless.readthedocs.io/
- fix bug in package.json devDependencies
- add CopyWebpackPlugin to the build workflow (this was almost a bug)
v2.3.0
V2.2.13
From version 2.2.0 to version 2.2.13 I've only had problem - and now fixed - with deployment to the wordpress plugin svn directory.
I'm sorry for the dirty repo history, but now I managed to get it back to work, in a more robust way and integrated Travis' Continuous Delivery.